On Fri, Feb 08, 2002 at 08:19:32AM -0500, Matt Cashner wrote: > On (02/08/02 00:02), Rocco Caputo wrote: > > > > If you have problems, questions, patches, let me know. > > > > Squirrels haunt my dreams, but I've learned to cope. > > you too? i thought it was just me. > > > > Speaking of new session types, do we have an official object layer rfc > > > yet? i was thinking of poking at that soon but i dont want to if there > > > isnt a consensus on it and an rfc. :) > > > > Sorry, no there. There are a buttload of willy-nilly notes, though, > > at: http://poe.perl.org/?POE_RFCs/object_layer > > > > Consolidating them will be a bit harder than combining the notes on > > signal fixes. It's a much bigger topic. > > see, signal's have rfcs and specs and previous implementations. near as i can > tell, object layer stuff doesnt share that. so, all you out there who care > about object layer stuff, get together, draft an rfc and i'll see about coding > it. deal? great.
Do you think you can cope with that ? :) There are people (like me) that like doing software design more than coding, and they will probably flood you with specs :) Coming up with a sound and _complete_ spec is certainly not easy, but making enough people (including Rocco ;-) ) agree on it is even harder. maybe we should take the classic approach and do analysis first. so what features and behaviour is wanted ? I would like the object layer to be or provide: -named parameters as in the wiki docs: -provide a good per method interface description, maybe with optional params etc. -a type system for all interfaces: -you need it if components can come from several authors, and certainly not all keep their code up to date etc. -version support ? -namespaces for objects: -objects need to be addressed across platforms and processes -something container-based probably, with interfaces on the outside edges -should enable tweaking of details without changing everything -> configuration, inheritance, modularity, ... -several other constraints -need to support all other features -migration of objects and distributed objects -(at least of attributes) -shared memory for objects -transparency: -people should not need to care about poe -pure oop and proper use of methods and asociations should be enough -same behaviour as Single System Image (Clusters) in the OS area -concurreny control: -the big solutions are too big for the beginning, use simple models first -several other things I cant and wont write a complete spec now. Other people's wishes might be totally different. All of that overlaps somehow with features that should be useful in P5EE (p5ee.perl.org). Some brainstorming is probably the best now. Torvald
