On Wed, 2002-04-10 at 04:48, Rocco Caputo wrote:
> On Thu, Apr 04, 2002 at 09:27:12AM +0100, Ian Stuart wrote:
> > I'm still playing around with POE - it seems to be the answer to my
> > problems: I have built a state-maintaining web demonstrator in a couple
> > of days - lovely!
> >
> > I can't determine the answer to my question form the docs, though I
> > think I understand it...
> >
> > Am I right in thinking that POE, by default, timeslices parts of a
> > single "process" - it does not fork a child process for each session.
> >
> > Yes?
> >
> > Assuming this, can anyone give me pointers in converting this
> > session-based system to the Run Wheel:
>
> [code snipped]
>
> What do you want the child process to do?
In this instance, I wish to have a seperate process to each image being
manipulated.
To recap: I have a system that loads an image, and then allows the
client to zoom and pan around the image.
The current system is threaded - so as the number of simultanious
clients increases, the available time for each client decreases.
As my production server is quite meaty, I think that forking off
resident processes to act for each client (using the central POE server
as a redirecting broker) would scale better. When I talk about scaling,
I'm talking about 100+ clients simultaniously accessing the system, and
each recieving response times of under 5 seconds :)
So, I want the server to accept an http request, and pass the request to
the appropriate child (based on the session ID - spawning a new child if
required). The child contains the image object.
I think it will be fairly trivial to have the server poke each child (to
persuade the abandoned ones to die.. [as it were] )
--
--==++
Ian Stuart: Edinburgh University Data Library.
Information is not knowledge
Knowledge is not wisdom
Wisdom is not truth
Truth is not beauty
Beauty is not love
Love is not music
-- Mary.
Personal web site: http://lucas.ucs.ed.ac.uk/
