I'm trying to decide on an approach and wondered if you guys ad any thoughts...
I'm wanting to build an app which functions as both server and client -
performing reasonably simple querying and file management between instances of
the app across a LAN.
each instance needs to keep it's own
On Fri, Apr 30, 2010 at 1:00 AM, justin webster m...@justinwebster.com wrote:
on the face of it coreData with bindings seems a good fit except for the
multi client nature of this project.
it seems like a few people have had a go at using Distributed Objects with
the coreData classes but the
On Apr 30, 2010, at 1:00 AM, justin webster wrote:
I'm wanting to build an app which functions as both server and
client - performing reasonably simple querying and file management
between instances of the app across a LAN.
each instance needs to keep it's own persistent data as well as be
