Re^2: POE and non-blocking XML/HTML parsing

You've said so little about what is driving this processing that is it difficult to see why you need multi-tasking?

Why not just start a new process for each url that fetches the XML and processes it?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^2: POE and non-blocking XML/HTML parsing

Replies are listed 'Best First'.
Re^3: POE and non-blocking XML/HTML parsing by Anonymous Monk on Apr 25, 2006 at 01:26 UTC
Because that's horribly inefficient when you're dealing with many, many data sources.	[reply]
Re^4: POE and non-blocking XML/HTML parsing by BrowserUk (Patriarch) on Apr 25, 2006 at 01:50 UTC
In what way inefficient? Your OS will timeslice those processes much more efficiently than any cooperative timesharing scheme; and most of the executable code will be shared between the processes by the OS also. By forcing what are essentially separate linear tasks to share a single process space, and using a user-level timesharing scheme with all of it's inherent overheads, you are preventing the OS from doing it's job efficiently. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal? "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]