On Sat, Nov 24, 2001 at 12:44:29PM -0500, Rocco Caputo wrote: > Good morning. > > About that object layer thing. A lot of discrete ideas are coming > together to form an object framework. I've put them together on the > web site: http://poe.perl.org/?POE_Design/Object_layer good work. but i'd like to see the non-blocking handler problem addressed or at least mentioned. people are used to writing code with calls that block and most modules do block as well. if we don't support this in a more convenient way than POE::Wheel::Run we will loose... threads aren't ready yet and probably won't be ready for some time.
i'd like to know wether someone on this list knows enough about perl internals and would want to work on http://poe.perl.org/?POE_Design/Pre-emptive_multitasking ? That would be a BIG help. It isn't the same as threads, can do less but has a smaller overhead (and one could have a lot of these pseudo-threads if the scheduler is able to handle them!). Your work wouldn't pass away when threads become stable ... :) > > Also the P5EE list has turned very interesting. They're discussing > component frameworks, standard APIs, exceptions, and a lot of things > necessary for a good object layer. At the very least, the projects > can cross-pollinate. See [EMAIL PROTECTED] or poe.p5ee on nntp.perl.org. Well, I haven't read all posts. But from what I have seen, they're talking about APIs and not about architecture. It seems all very web centric as well, people asking if persistence is actually needed and similar discussions. Anyway, that's just what I have read so far... Back to the topic, I do think there is a lot missing now. Sometimes I feel like I should write down my thoughts about it, but it wouldn't be a complete specification. So, would you be interested in something incomplete ? Torvald
