On Jul 20, 2006, at 8:16 AM, Joao wrote:
I know what you mean. Unfortunately, I have already 3.000 clients from different vendors communicating with a C version of the program. All of them using UDP. I know it is hard, but I need to have a kinda session per terminal. Actually, I already have a kludge that works. I was just wandering if I could use the Acceptor newSession method for this.
not cleanly.. since you presumably have some custom logic that lets you determine which packets are part of a "session" ?
I quickly read the code, unfortunately I could not figure out how to use it, once I will create the session later after receiving the first message from that terminal. Just at that time I will have enough information to create it(for example the remote address).In case anyone has a clue on how to use it, I will appreciate.
one thing you can do it put your session-determination code into an IoFilter, and then wrap the message in your own object when passing down to the next filter / your handler that adds session information.
-pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
