Re^3: How to transmit complex data to client?

Ok, a select based server would not be either multi-threaded or multi-process. A select server is the least commonly implemented server model and is normally used for special high-performance response-time applications.

So what?

I doubt the OP has implemented a select server model.
A fork-based server is much easier to implement.

I think the OP should show a simple set of client <-> server code.
I am very sure that Monks will help iron out the details if the OP gets "close to the goal".

Comment on Re^3: How to transmit complex data to client?

Replies are listed 'Best First'.
Re^4: How to transmit complex data to client? by JavaFan (Canon) on Aug 29, 2011 at 14:57 UTC
Even easier is to write a server than neither forks, uses threads, or even has a select loop. Call it a hunch, but I don't get the impression the OP is creating a large service which requires many clients to connect concurrently, each doing massive data transfers. If it's just one or a few clients who connect to the server infrequently, doing a single request for which data can easily be send back to, a simple server that does accept, read, send in a simple loop is often good enough (Been there, done that, didn't get a t-shirt). Not that the OP was asking how to write a client server system.	[reply]
Re^4: How to transmit complex data to client? by zwon (Abbot) on Aug 29, 2011 at 14:35 UTC
A select server is the least commonly implemented server model Oh, really? I use event based model quite often, because it simple and resource efficient. Not only when I need performance, but when for example I have many long living connections with low traffic. Also if you look onto amount of modules that support this model (like POE, or AnyEvent) you wouldn't call it "least common".	[reply]