On 8/28/06 3:34 AM, "Tore Halset" <halse..vv.ntnu.no> wrote:
> On Aug 28, 2006, at 4:05, Watkins, Garry wrote:
>
>> I ran into the error 500 with Hessian 3.0.20. I finally had to
>> track down a 3.0.13. But I got it going late last night.
>
> Yes, we should probably fix CAY-636 sooner or later.. It can be a bit
> complicated to get started.
>
>> Extended
>> NSManagedObjectContext - which should encompass faulting
>> NSPersistentStoreCoordinator
>> NSManagedObjectID
>
> Will it be possible to have the client side implementation of
> ObjectId subclass NSManagedObjectID or do we need two different
> classes for this?
>
I think that we should be able to use one subclass for this, but I am still
looking at how to set the NSManagedObjectID, Apple is not exposing a lot of
the CD API. Hopefully, I can figure this out in the next day or two.
>> Created my own classes since these aren't exposed by CD
>> ObjectStore
>> TransactionalObjectStore
>> CayenneObjectStore (I am just starting implementing this)
>> WebObjectsObjectStore (Planned for the future)
>
> Lots of ObjectStores. What are the difference between them? I have
> not done any ObjectStore stuff yet - Multiple object with the same
> ObjectId can exist in the same context now. Must of course be fixed..
>
ObjectStore and TransactionalObjectStore are abstract classes.
Transactional is there in contrast to Apple's CD stuff mentioned at WWDC
which is NDA. Cayennne and WebObjects are the implementations. If you did
not know WebObjects has a remote client layer as well. However, their
protocol is not documented. What are you using to monitor the traffic over
port 8080? I am sure that I could use that to watch the WebObjects stuff.
>> Hopefully, I will have some time this week and we will get to
>> integrate it
>> all together with the stuff that you have been doing.
>
> Cool.
>
Can you check in your latest stuff with the faulting? Maybe I can piece some
of this stuff together later today.
I already broke you project apart and created a Framework. It was not too
difficult. Just create a new Cocoa Framework. Copy all of the files from
(CAYClient) to the new Project via drag and drop that should be in the
Framework. Then delete the files out of CAYClient. Put a project reference
in CAYClient to the new framework. Then finally, copy the ???.framework to
the product linking phase. Then you should be golden. If you would like, I
will build the framework project for you, and zip it up and send it to you.
> Currently, I am wondering if we need a NSArrayController subclass to
> get the "add:", "insert:" and "remove:" bindings to work. Or perhaps
> create an CAYManagedObjectArray (and/or CAYToManyArray) that
> automatically register new objects in the context and set the correct
> relation.
>
> - Tore.
-- Garry WatkinsDatabase Administrator Motley Rice LLC 843-216-9639
Confidential & Privileged
Unless otherwise indicated or obvious from its nature, the information contained in this communication is attorney-client privileged and confidential information/work product. This communication is intended for the use of the individual or entity named above. If the reader of this communication is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and destroy any copies--electronic, paper or otherwise--which you may have of this communication.
This archive was generated by hypermail 2.0.0 : Mon Aug 28 2006 - 08:10:39 EDT