Re (tilly) 1: Multiple clients with IO::Sockets

If you are not wedded to any design yet, give some serious thought to whether or not you can skip the custom server and client, and just write a web interface on an internal webserver.

http is well understood, both clients and servers are freely (and widely) available...

Comment on Re (tilly) 1: Multiple clients with IO::Sockets

Replies are listed 'Best First'.
RE: Re (tilly) 1: Multiple clients with IO::Sockets by swiftone (Curate) on Sep 08, 2000 at 20:16 UTC
If you are not wedded to any design yet, give some serious thought to whether or not you can skip the custom server and client, and just write a web interface on an internal webserver. My first thought, believe me. However, the client end requires lots of manipulations that could only be achieved through (shudder) javascript, there is a chat aspect to it (and we know how unfriendly the PM Chatterbox is when you can't reload the page often), and finally, I want the design to be portable to non-Unixen. (i.e. internal webserver may not be easily available).	[reply]
RE (tilly) 3: Multiple clients with IO::Sockets by tilly (Archbishop) on Sep 08, 2000 at 20:26 UTC
Even so, you could (my turn to shudder) use a protocol built on http like SOAP then build the front end client from there. As for finding an internal webserver, that is generally not a problem. On Windows I have recommended Xitami to a number of people with success. Free, easy to set up, works. At the least this gets you out of writing and debugging the server...	[reply]