On Aug 15, 2006, at 16:02, Watkins, Garry wrote:
I was thinking of taking advantage of the Core Data (CD) to manage the
ObjectContext handling. I spoke with one of Apple's Core Data team @
WWDC, and he is going to provide me with a sample of a MemoryStore
that
has been extended to work with some sort of web service. If we can
leverage this code we could just pick up the added/changed and deleted
objects and pass them back to Cayenne to process them and put them
back
into the database. Plus we get all of the binding stuff for free.
Cool.
Most of the cayenne objects sent over the wire using the protocol
will probably have to be implemented with or without the Core Data
client. Most of this is boring port of code. Like ObjectId that now
has 3 ways to encode a unique key. 1 - Temporary, 2 - Single key, 3
multi key. Getting the isEqual correct and hash efficient are not
that easy - at least for me :)
So, if we use a Core Data client or write our own stuff, a lot will
probably be common.
I have emailed bryan about his HessianObjC webpage and he fixed the
problem. He will also set up an maillist, but I have already sent him
my first questions. I included the questions in the bottom of this
message.
- Tore.
Authentication. Have you tried it with basic http authentication.
How do you set it up? I am currently testing this without
authentication.
I sometimes get NSError-objects. All the rest of the objects seem
to be in place. It looks likt this:
- NSError "Unknown tag returned from server "
Domain=BBSHessianObjCDomain Code=666 UserInfo=
{NSLocalizedDescription = "Unknown tag returned from server "; }
- NSError "Unknown tag returned from server "
Domain=BBSHessianObjCDomain Code=666 UserInfo=
{NSLocalizedDescription = "Unknown tag returned from server "; }
Sometimes the server return an object structure with several links
to the same object. In NSLog()-output the datastructure has one of
the references ok, but the others seem to just include a number.
Looks like this is related to the NSError-issue mentioned above,
but I am not 100% sure.
Otherwise, I find it easy to use. Very nice that all custom objects
are decoded as NSDictionary as it makes key-value coding work and
NSLog can print out the structure very nice. It is also nice that
is uses NSCoding.
