Re: [Modeling-users] N-tier development and modeling
Status: Abandoned
Brought to you by:
sbigaret
From: Federico H. <fh...@vi...> - 2004-03-07 22:05:48
|
On Thu, 2004-03-04 at 18:06, Tom Hallman wrote: > Here is the situation: my colleagues and I are attempting to put toget= her=20 > a framework using an N-tier methodology, with the client software=20 > interfacing to the server/database backend via remote procedure calls (RP= C).=20 > For us, Modeling will serve as a large part of that backend, with an API=20 > written overtop. The client will make calls to this API, and all will be = grand. Maybe I'm missing someting here... =BFbut are you sure that this ought to be solved in Modeling itself? I can't help but refer to Modeling's ancestor: EOF within OpenStep. In OpenStep, you would use EOF to get object/relational persistence, and if you wanted to do n-tier deplyment you'd resort to Distributed Objects, which were orthogonal to EOF (i.e. any app could use either one, or both, or none). So maybe what you are looking for is not a Modeling extension, but a network-transparent message passing system for Python, which can be used together with Modeling? 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 |