On Wed, Feb 05, 2003 at 01:49:59PM -0800, Phil Crow wrote: > I'm working on a scheme to make remote access to > persistent Perl objects simple. I'm writing to ask > for advice of all kinds, including naming and > functionality. > > UPSHOT of my approach > > The class being exposed doesn't even know.
[...] > MY QUESTIONS > > Is anyone interested in this aggressive simplification > of client and server API's? > > Would a server helper module like OOPersistServer be a > candidate to be a genuine POE::Component::Server? The lack of response to this message seems to indicate no. :( I think it's a matter of people not understanding the usefulness of the project. Can you show some common cases where OOPersistentServer would simplify people's lives? > If this were your code, how would you name the pieces > for CPAN? Unfortunately I cannot say. It seems that the concept overlaps remote persistent objects and remote method calls. Which is it more like? -- Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
