[lwip-users] Re: [lwip] reusing a socket from runtime to runtime

[mt]

You could (if you're a...)

hacker:
implement a second server application that runs over
udp and provides persistent tcp state maintenance for
the clients.  whenever your client powers up it would
check in with this server to see if it has a tcp
connection, and if so, it would get the params for the
connection (that's the tricky part) and start using it
(that too). the state server would need to have access
to the server's low level tcp "stuff".

pragmatist:
another possibility (probably better) would be to just
use udp for the main app transport.  since you dont
seem to be guaranteed power to begin with, losing a
message or two isnt your app's end of the world? (and
even that's not necessary if you have time to code
around it.)

regards
mt

> A few ideas spring to mind to work around this
> (although I haven't
> thought them fully through)
> 
> 1) I could periodically poll the connected clients
> from the server app
> and drop any clients that do not respond.
> 2) I could simply open a socket, send data and close
> the socket for each
> message. This is obviously at a significant overhead
> and loss of power
> during any communication will bring about the same
> problem.
> 3) I could re-implement the section of code that
> generates a port number
> to provide one that is random and maybe this is what
> I should do.
> 
> QUESTION:
> 
> Does anyone have an identical or similar experience
> of a situation like
> this and if so could you shed some light on possible
> ways to overcome or
> work around the problem. Maybe I am just missing
> some understanding of
> sockets due to my limited experience but any help
> will be most
> appreciated.
> 
> Best regards,
> 
> Jimi
> [This message was sent through the lwip discussion
list.]


__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
[This message was sent through the lwip discussion list.]