> > Yes, asynchronous behaviour definitely makes things more complicated. I > don't know about there not being a need, however. You might want to be > requesting multiple things at once. Of course, the client could open up a > new connection in a new thread for each request. That's how I'd prefer to > do it, but I'm not sure if it's the best way.
Not really necessary to have another connection, but another thread, yes. > > True. So you think that the connection should stay open and send more > messages instead of closing the connection and opening a new one for the > new message thread? I'm refering to places where we need to return from accepting a Reply to wait for another message. RequestClient currently needs to listen for a StoreData message following the Reply, for instance, as well as being able to drop out of handling a Reply to wait for a QueryRestarted on data restarts. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20000807/99a7a7ff/attachment.pgp>
