CouchDB could be an inspiration (the document architecture should also be flexible enough to work with CouchDB almost out of the box, since it's RESTful)
> --
> You received this message because you are subscribed to the Google Groups "Cappuccino & Objective-J Development List" group.
> To post to this group, send email to objecti...@googlegroups.com.
> To unsubscribe from this group, send email to objectivej-de...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/objectivej-dev?hl=en.
More importantly, it's actually one of the pieces of Cocoa that may have aged the worse. On the desktop, it has largely been replaced by CoreData and custom formats. And server apps have shown us that most things are much more likely to be broken down into small pieces of data stored in a database, versus a single blob that can be loaded and saved once.
So one approach might be to simply move forward with a CoreData like system either as part of or in place of any work on CPDocument. I think Saikat probably has a lot to add on this front as well since they're doing interesting things with documents.
On Dec 8, 2010, at 9:14 AM, Francisco Tolmasky wrote:
The issue is, I think, that CPDocument makes a lot of assumptions
about how you persist your data (also a slight nit -- i don't think it
is entirely restful -- the overwrite request and and CPSaveOperations
should be PUT requests, for example (might not even need the HTTP
header)). I thought about talking a bit about the unusual things we
do and which of CPDocument's assumptions are the ones that have caused
us to rewrite a parts of it, but none of the things we do really seem
that useful in the general use case, and I think that's entirely the
issue - many people will have a non-generalizable use case here. I
think we I agree with Tom/Ross that there should be some default
persistence solution (I don't know a lot about CoreData), but I think
we just need to be really good about making it clean and easy to
switch this part out as many people will need to (and currently,
overriding the server-interacting behavior in CPDocument is a bit
messy).
I also like the idea of having offline support via local storage
automatically in Cappuccino apps.
If you guys want, I can go through the parts of CPDocument that we've
overridden and why, but not sure how useful that will be if we want to
move to a different model entirely.
I am interested in your proposal, and actually the design looks good!
So could you share some of your updates if you have made improvements on this?
Thanks,
Takenori