Re: 3T Relationships [are done]

From: Tore Halset (halse..vv.ntnu.no)
Date: Thu Sep 15 2005 - 16:20:01 EDT

  • Next message: Andrus Adamchik: "Re: DataContextFactory"

    On Sep 15, 2005, at 22:17, Tore Halset wrote:

    > This is the way I was thinking..:
    > * The objects and the object graph are edited on the client side
    > using the client classes.
    > * The client calls commit
    > * The client logic sends the diff to the server context
    > * The server propagates the info to the server classes. If person's
    > fullName changed on the server, call Person.setFullName with the
    > new value on the server.
    > * The server context commit
    >
    > Same thing should happen on query. I think the result of the query
    > should be put into the normal server classes (like _Person and
    > Person) and the serializer (xml, hessian, whatever) should issue
    > all the get* methods on the objects.

    Sorry, I meant Person (not _Person) here.

    > It should be possible for the app developer to have some logic in
    > the server classes and some other logic on the client classes.
    >
    > I do not know if this is the way to do it. Just some thoughts...

      - Tore.



    This archive was generated by hypermail 2.0.0 : Thu Sep 15 2005 - 16:20:08 EDT