Since some discussion has started I think it is time
for my true confession. Though I love Perl, I am
really mostly a Java programmer. My intent with the
project I mentioned is to provide schemes like Java
has, but with a heavy Perl spin. With them I might
some day convince my employer that
: Wednesday, February 12, 2003 6:11 AM
To: [EMAIL PROTECTED]
Subject: RE: RFC: Persistent Object Client/Server Scheme
Since some discussion has started I think it is time
for my true confession. Though I love Perl, I am
really mostly a Java programmer. My intent with the
project I mentioned is to provide
On 11-Feb-2003 Rocco Caputo wrote:
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. :(
In my case, lack of response means I'm busy. Object persistance is
something I've
Beans. someday I foresee a nice mixture of this with
IKC to do replication stuff.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 11, 2003 12:06 AM
To: Rocco Caputo; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: RFC: Persistent Object
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.
Unfortunately I cannot say. It seems that the concept overlaps remote
persistent objects and remote method calls. Which is it more like?
I think there would be a better response for this project if these concepts
were implemented individually (or in a component nature) permitting more
