Re: [Modeling-users] N-tier development and modeling

[Federico H. <fh...@vi...>]

On Tue, 2004-03-09 at 19:35, Matthew Patton wrote:
> 	Tom Hallman and I work together, so I speak for both of
> us.  Numerous comments below:

Matt,

I think I understood what you were saying, but obviously you didn't
quite understand my response, which is my fault, of course. You will
find numerous references to NeXTstep and OpenStep in the Modeling
mailing list, as many of us come from that background, and Modeling
itself is a loose reimplementation of EOF (a technology first released
as part of NeXTstep) in Python.

Now, the code that you included would work quite differently in the
NeXTstep environment, for instead of doing the CORBA thing, we'd just
ask a server for a remote editing context. The local process would get a
proxy object, that works like it's local, but in fact forwards all
requests to a real editing context that lives in the server. We'd then
query the database using this editing context, instantiating objects in
the server, for which the Distributed Objects mechanism would create
proxies in the local address space. The whole IPC thing then happens
behind the scenes (aside from a few memory deallocation issues, the
programmer thinks he's dealing with local objects --- we can later argue
whether this is good or not).

My point was that, given that Modeling is an EOF reimplementation, it
might be rewarding to explore the possibilities of using something that
replicates the Distributed Objects functionality to achieve your goals.
Marcos pointed out in the list that Pyro might be such a beast...

Regards,

	Fede

--=20
GnuPG Public Key: gpg --keyserver wwwkeys.eu.pgp.net --recv-key BD02C6E0
Key Fingerprint: 04F4 08C5 14B7 2C3D DB21  ACF8 6CF5 0B0C BD02 C6E0