I had a breakthrough with nested contexts last week - we can use the
same mechanism that we use for communication between contexts in the
multi-tier environment. This sounds obvious, but it wasn't until all
the main pieces got in place. I tentatively called this mechanism OPP
(for "Object Persistence Protocol"):
http://cvs.sourceforge.net/viewcvs.py/cayenne/cayenne/src/cayenne/
java/org/objectstyle/cayenne/opp/
So we have a plan and 70% of the implementation, but there is still
more than a few loose ends. Main one is reconciling DataContext with
ObjectContext API (including a common EntityResolver and ObjectId/
GlobalID mismatch), but also there are parent-to-children
notifications that are still missing from OPP.
So we are getting there, but not quite there yet...
Andrus
On Sep 27, 2005, at 12:26 PM, Mike Kienenberger wrote:
> Chris,
>
> Yeah, I think the biggest piece to get working is handling
> notifications.
>
> The rest of the implementation is probably fairly straightforward,
> especially if you let Andrus figure out the remote nested DataContext
> stuff :)
>
> I haven't had time to work on this yet as I have a lot of other
> higher-priority tasks, so feel free to take the lead.
>
> http://www.objectstyle.org/cayenne/lists/cayenne-devel/
> 2005/02/0006.html
>
>
> On 9/27/05, Cris Daniluk <cris.danilu..mail.com> wrote:
>
>> I noticed that the nested context stuff is still listed as
>> preliminary
>> in the wiki. Is this more refined in CVS? I would love to start using
>> it, as I'm desperate for the functionality :)
>>
>> Is there anything that can be done development-wise to help it along?
>>
>> Cirs
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Tue Sep 27 2005 - 15:16:44 EDT