shemp has asked for the wisdom of the Perl Monks concerning the following question:
Basically, there will be one server process that listens for requests for information. A base request will supply about 10 values, passed all at once and expect about 20 values returned all at once. Then the connection will be ended.
I was thinking of using XML::Simple to format data passed between the server and clients. I dont want a lot of overhead, but i cant just use positional params or something like that because not all requests will provide exactly the same amount of info, or return the same amount of info. So if i keep the tag names short, i dont think i'll incur too much overhead.
The server cannot be forking, because the result of one response will affect subsequent responses, so the server will need to fulfill requests one at a time. And, most requests to the server will be coming from a different machine than the server is running on.
So i guess this boils down to 2 questions:
1) Does the overall plan seem reasonable?
2) Is XML::Simple a good way to go, or should i use something else for the communication syntax?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Interprocess communication design
by perrin (Chancellor) on Sep 16, 2005 at 17:47 UTC | |
by shemp (Deacon) on Sep 16, 2005 at 20:59 UTC | |
|
Re: Interprocess communication design
by cmeyer (Pilgrim) on Sep 16, 2005 at 17:48 UTC | |
by shemp (Deacon) on Sep 16, 2005 at 18:15 UTC | |
|
Re: Interprocess communication design
by samtregar (Abbot) on Sep 16, 2005 at 17:43 UTC |