> If the context-switching overhead turns out to be too high, then I will do
> exactly that. But it will mean maintaining state for each connection, and
> that state will only grow more complex with future enhancements by myself
> and others.
Umm, huh?! If you don't maintain state for each connection, how will you
know what to do with the data you get?
> The big draw to Pth for me is the simplicity of threaded code
> with the efficiency of a state machine. At least, I think it will be
> efficient. I don't actually know at this point exactly how expensive a
> context-switch in Pth is.
Simplicity is achieved when you precisely understand what the state is.
DS
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
Development Site http://www.ossp.org/pkg/lib/pth/
Distribution Files ftp://ftp.gnu.org/gnu/pth/
Distribution Snapshots ftp://ftp.ossp.org/pkg/lib/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
