Re: Eu v4.0 suggestion
- Posted by Kat Feb 28, 2009
- 852 views
Socket.e should not need a new release if there was new code for doing http. If someone added MUSH interface, they'd haveto release a new sockets.e. If the protocol for a given transmission using sockets.e was not part of sockets.e, then the newprotocol.e could be worked on and distributed separately.
Remember, i worked on sockets.e.
Yes, I do remember. What I am saying is that socket.e shouldn't go away. I am not saying add http support to socket.e, it would be good to be in it's own file, such as std/net/http.e, std/net/pop3.e, std/net/imap.e, etc... But those would include std/socket.e and use socket.e's underlying socket implementation, as it has done all the hard work of wrapping platform specific network functions.
Jeremy
Of course. I agree. I thought i said that.
Kat
