Tom Hallman
2004-03-12 15:54:01 UTC
Greetings Sebastien and all,
I have a few questions regarding a client/server implementation using
Modeling. I will do my best to make this as clear as possible =)
Let's say we have a client and a server, with a protocol (like XMLRPC)
between them that passes along objects and their member variables.
Modeling-generated classes reside on the server, while skeleton classes that
define the same method interface as the Modeling classes reside on the
client. When a call is made to a method on the client side that does not
locally exist, it will go out to the server to use the method that is
defined there. (This way we can write really "dumb" clients when necessary.)
The most important question is this: is it possible to pass a modeling
object back and forth over the RPC transport? (a related question is, are
Modeling classes picklable?) Will we lose or "dirty" important context
data? Other than the basic member data of a class (like for an Address
class: city, state, etc.), what data do Modeling objects maintain (I know
one such thing is the global ID)? Perhaps another way of phrasing this is:
could two Modeling objects that have the same global ID and basic member
data be interchanged without side effects?
Thanks in advance for any insight!
Yours,
Tom
___________________________________________________________
Tom Hallman DiscipleMakers, Inc
***@dm.org http://www.dm.org/~hallmant
531 Brittany Dr * State College * PA * 16803 * 814-861-4591
Go therefore and make disciples of all nations (Matt 28:19)
I have a few questions regarding a client/server implementation using
Modeling. I will do my best to make this as clear as possible =)
Let's say we have a client and a server, with a protocol (like XMLRPC)
between them that passes along objects and their member variables.
Modeling-generated classes reside on the server, while skeleton classes that
define the same method interface as the Modeling classes reside on the
client. When a call is made to a method on the client side that does not
locally exist, it will go out to the server to use the method that is
defined there. (This way we can write really "dumb" clients when necessary.)
The most important question is this: is it possible to pass a modeling
object back and forth over the RPC transport? (a related question is, are
Modeling classes picklable?) Will we lose or "dirty" important context
data? Other than the basic member data of a class (like for an Address
class: city, state, etc.), what data do Modeling objects maintain (I know
one such thing is the global ID)? Perhaps another way of phrasing this is:
could two Modeling objects that have the same global ID and basic member
data be interchanged without side effects?
Thanks in advance for any insight!
Yours,
Tom
___________________________________________________________
Tom Hallman DiscipleMakers, Inc
***@dm.org http://www.dm.org/~hallmant
531 Brittany Dr * State College * PA * 16803 * 814-861-4591
Go therefore and make disciples of all nations (Matt 28:19)