Adam Langley <[EMAIL PROTECTED]> writes:
> I could put it in a thread. Each client would have 2 (or more)
> threads. One would be neuroses and the rest would be the client.
> Client and Neuroses would communicate via a socket pair. Even with
> shared libraries, this could be quite bloated. (thou nothing like
> fred is ;)
> The final solution (unless you have others) is to have a seperate
> process which clients could connect to, and which would forward
> messages to a local node. It's basically the same as the last
> solution except that the node would be minimal (without a
> DataStore) and would just forward requests.
I actually wouldn't even force it off into its own thread or process,
but make that an option for client authors. A client that uses
neuroses could be written very similarly to a program that uses GTK --
it calls a blocking function to handle events, and waits for
callbacks. If it has other things to do, it can thread or fork off
(as the author sees fit) to do those things elsewhere.
-S
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
