|
>Do these different clients need to be >able to talk to each other directly? At first I was going to say "yes" but I am re-evaluating that. >If not, you'd probably be better off using the >paradigm in chapter 7 of my sockets tutorial. >[spawn multiple jobs to process the commands] Already looking into that! >Finally, if all else fails, you'll be stuck with >the "state machine" type server. Very few different >server apps have a lot of different states. Hm. Maybe I'm complicating things too much. >Perhaps the server should just be executing >"commands" send by the client, >and the sequence of those commands should >be determined by the client? That's the general idea, but I need to enforce the authentication process before anything else can occur. Thanks for the good ideas! --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.