I used to have a demo program "back in the day" that I used for some of my conference talks. I used to install a remote proxy in a rexxtry session in one window that redirected stdin/stdout to the another window via tcp/ip and allowed me to control what was going on. Conceptually, this was a proxy very similar to the monitor class, and worked fairly well for what it did.
Of course, the limitation was only string method arguments and results could be marshalled back-and-forth. A more general solution will require something like Java serialization or generated helper classes like are used CORBA. Rick On Tue, Jul 21, 2009 at 3:07 PM, David Ashley<david.ashley....@gmail.com> wrote: > All - > > I want to start a discussion on an idea I have been thinking about for a > while: remote ooRexx classes. The idea here is something like Java beans > in than a program executing on one machine can access and use a class > and its methods that exist on another machine - sort of an RPC mechanism > for classes/methods. > > I don't really have a fixed idea about how this would all work I just > know that it would be a really nice feature for ooRexx. I can think of > all kinds of ways I could use this every day. > > So I am open for ideas on how the architecture for this might be defined > and work. Let the discussion begin. > > David Ashley > > ------------------------------------------------------------------------------ > _____________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
