On Friday, March 22, 2002, at 05:14 PM, Matt Sergeant wrote:
>> every time i look at poe my head spins and i am reminded >> exactly how much of a novice i really am. > > I had this problem too, until I figured out that it's just terminology > that was confusing me. That's why I'm giving a POE tutorial at the perl > conference this year to help clear up some of this confusion. > Conceptually > POE is actually really simple, once you get past the documentation ;-) Ok, that is good to hear. I always thought I was too ignorant too understand it ;) I suppose POE indeed uses a somewhat strange terminology (wheels?). But isn't it a point of p5ee to normalize/standardize the terminology? In that respect, would it be possible to use POE at a lower level underneath an API(s) that is more in line with p5ee, terminoloy-wise? I don't understand enough of it to assess that. A thought: would it be possible to somehow use POE as a container in which Wombat runs? Though Wombat is intended to run servlets in it might be generalized to run general handlers that are run upon receipt of a request with the addition of timers etc.. On the other hand, POE is about cooperative multitasking I believe which might not be such a good base to start with... In a more general way I think p5ee needs something to easily implement a "components with services" architecture (which I partially "solved" by using an Apache/mod_perl instance per component and HTTP/Storable for services). Regards, Bas. ---- Unix _IS_ user friendly... It's just selective about who its friends are.
