On 29-Nov-2001 Rocco Caputo wrote: > Probably done in POE::Object or POE::Component or something. I'd like > to see the object layer get away from Session as the unit of > interaction. Sessions just aren't built for it, and I don't see a > reason to make them into it yet. > > Maybe I'll figure it out in the spring and it'll all be good.
I've writen (and am going to deploy ANY DAY NOW) JAAS (just another app server) which includes an "object layer" we *cough* argued over at the begining of summer. I need to finish documenting it and start showing it to folks. Roughly, the object layer has the following properties: - objects are perl objects. As much as possible, they look like regular method calls. In fact, ideally a method could be invoked directly or via POE. - all access to POE is via JAAS::Services, which does some pretty messy things at times. - each object is attached to a session that accepts/sends events - JAAS methods are declared via a hash that a method called 'method()' returns. An object's session calls this method when the object is attached to it. > POE has pre-5.6 users, and I don't want to break the parts they're > already using. That doesn't mean new parts can't use present-day > features, though. And then there's me, still running 5.004_05. :) However, I'm supposedly writing extensive regression tests that will allow me to upgrade do 5.005 or even 5.6 in a sane fasion soon. -Philip
