Re: How to efficiently manage bunch of processes

Sorry to post a non-responsive reply, but I feel I have to comment on the following:

After few hours of scanning through POE docs I'm begginng to think that it's more of cool-idea then working system.

Perhaps you meant it's not workable in your case, and you may well be right about that. There are many times when POE is not the right choice, and many times when it would have been the right choice, but rewriting lots of code is not worth it. No reasonable person would disagree with that, and if that's what you meant, then please ignore the next paragraph.

If, however, you meant what you literally wrote -- that POE is not a "working system" -- then you are dead wrong. I've used POE for numerous projects in the short time since I first learned it. I have quite enjoyed those projects. It is definitely a working system, by any definition of the term. Furthermore, to make such a statement after simply scanning the docs is foolhardy and silly. I know (from experience) that POE seems rather strange at first, and it takes some actual use before it clicks. Once it does, things start to make a whole lot of sense, and it becomes a very nice system. Perhaps you will give it a shot with another project sometime.

PS: I hope this reply isn't taken the wrong way; I really am attempting to clear up what seems like a possible case of misunderstanding. I write with the best intentions.

Comment on Re: How to efficiently manage bunch of processes

Replies are listed 'Best First'.
Re: Re: How to efficiently manage bunch of processes by flyingmoose (Priest) on Mar 19, 2004 at 14:48 UTC
I looked at POE, but it makes you re-design your whole app around it, and for my needs I'd have to recreate some of basic POE components to suit my app. After few hours of scanning through POE docs I'm begginng to think that it's more of cool-idea then working system. Rocco would probably disagree, but in my experience POE does try to change your app. It is, however, a very cool infrastructure -- though if you want to design your lightweight message-broker/event-handler, that's not such a bad thing to do -- it keeps you from having to POE-ify your app, and you learn something from reinventing the wheel. If you were starting something ground up though (and you know the interdependencies will be complex), POE is a good choice. It sort of feels like programming an embedded system or a microcontroller sometime, the programming style is very very different -- your just can't attack the same problems in the same ways.	[reply]

Replies are listed 'Best First'.

Re: Re: How to efficiently manage bunch of processes
by flyingmoose (Priest) on Mar 19, 2004 at 14:48 UTC

I looked at POE, but it makes you re-design your whole app around it, and for my needs I'd have to recreate some of basic POE components to suit my app. After few hours of scanning through POE docs I'm begginng to think that it's more of cool-idea then working system.

If you were starting something ground up though (and you know the interdependencies will be complex), POE is a good choice. It sort of feels like programming an embedded system or a microcontroller sometime, the programming style is very very different -- your just can't attack the same problems in the same ways.

[reply]