On Tue, Jul 06, 2010 at 10:55:21PM +0100, Tim Retout wrote:
Two options I'm not keen on are: 1) one fork per packet, and 2)
limiting netsed to at most one client.
Sure, I didn't want that either...
I've got a vague intuition that for each new client, you will be able
to create a new socket
On Tue, Jul 06, 2010 at 12:08:01AM +0100, Tim Retout wrote:
On 5 July 2010 23:38, Julien Viard de Galbert jul...@vdg.blogsite.org wrote:
* whenever a client send a datagram to a server it expects one and only
one datagram back
I think this is quite limiting. There is no concept of a
On 6 July 2010 09:51, Julien Viard de Galbert jul...@vdg.blogsite.org wrote:
But for the way back, server to client it's different:
The server will likely send a message back to the client, that is to say it's
IP and port number (this one is dynamic!).
So with netsed, the server sends a
Hello fellow netsed interested people ;)
netsed does not have UDP support, I plan to implement it, but it's not as easy
as it seams:
UDP is by nature not connected, so it's not possible to know when the client or
server has closed it's socket...
As the requirement are not clear (I guess user
On 5 July 2010 23:38, Julien Viard de Galbert jul...@vdg.blogsite.org wrote:
Hello fellow netsed interested people ;)
netsed does not have UDP support, I plan to implement it, but it's not as
easy as it seams:
UDP is by nature not connected, so it's not possible to know when the client
or
5 matches
Mail list logo
