Actually we are talking about distributed DataContexts. So DataObjects are
not "remoted" in any traditional sense.
One of the upcoming 1.2 features is nested DataContexts in the same VM. So
a "child" DataContext can commit to a "parent" without committing all the
way to DB. This is ideal for things like dialogs and multistep web
screens.
"Distributed" DataContext will likely be implemented as an extension of
"nested" DataContexts feature with remote parent. Communication between
parent and child will be abstracted into a separate layer and will be
pluggable (I am looking at Hessian for one possible default
implementation).
We'll have more discussions on that as we start the actual work.
Andrus
> Just out of curiosity, when we talk about distributed objects, are we
> talking about client-side delegates that use RMI or similar technology
> to blindly relay all requests, or are we talking about more "smart"
> distributed objects that can cache their values locally, etc?
>
> Cris
>
>> > is there any work going on in this direction? ist there any plans?
>>
>> I am designing it right now. I actually started looking at what client
>> technologies we have to support and potentail pitfalls with
>> them (e.g. see
>> this lovely thread on Apple's webobjects-dev:
>> http://lists.apple.com/archives/webobjects-dev/2005/Mar/msg00177.html)
>>
>> You are welcome to post your experiences/comments here. The
>> whole thing
>> should start moving pretty soon.
>>
>> Andrus
>>
>>
>>
>>
This archive was generated by hypermail 2.0.0 : Mon Mar 14 2005 - 09:34:52 EST