Ipv Six Work Note

Not logged in

• Browse
• Help
• Home
• Login
• Reports
• Search
• Timeline
• Wiki

• Contents
• No-Diff
• Text

 
 I do not think we need any class that encapsulating those BSD socket interfaces.  The reason is that I do not change any semantics of BSD socket interface but only syntax. Or, if you suggest just a c++ namespace, I would certainly accept that.
 
-Also, I am skeptical to another socket interface layer since we already have socks, reli_sock, and so on. BSD socket interface is kinda universal since it even ported to Playstation Portable programming interface.
+Also, I am skeptical to having another socket interface layer. For application socket classes, we already have Sock, ReliSock, and so on. Any abstraction other than proxy between application socket classes and BSD socket interface? I am not thinking in that way. BSD socket interface is kinda universal since it even ported to Playstation Portable programming interface. If you have any idea, please let me know.
 
 {section: Todo}
 Manageable daily work-list.

This work is supported by NSF under Cooperative Agreement OAC-2030508 as part of the PATh Project. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF. Site built using CVSTrac.