Re: Client-Server Design with Cocoa, Bindings and maybe CoreData?
Re: Client-Server Design with Cocoa, Bindings and maybe CoreData?
- Subject: Re: Client-Server Design with Cocoa, Bindings and maybe CoreData?
- From: Isaac Csandl <email@hidden>
- Date: Fri, 29 Jul 2005 10:22:24 -0500
(I pasted this from the web archive, apologies for the incorrect
formatting & headers)
I'm looking for an answer to this question too, so I just want to
reiterate it.
Justin, have you found out anything? I'm in the same boat with you,
especially that "bane of my existence" part regarding FileMaker.
I'm looking at Distributed Widgets as an interesting example, but it
was clearly written before Core Data. http://www.kavasoft.com/
DistributedWidgets/
Anyway, that's at least two of us looking for an answer to this
question. I'd really like to know if it's even possible (or if it's
just too much of a hack at this point).
--Isaac
Client-Server Design with Cocoa, Bindings and maybe CoreData?
FROM : justin1
DATE : Fri Jun 10 00:57:57 2005
I've been playing around with CoreData for a little while, trying
to get it to do some tricks, and so far it's been pretty good
outside of a few quirks.
But now I'm coming to the real purpose of my experiments: to
replace a FileMaker solution that has been the bane of my existence
for a while. I'm used to MySQL/Java, but client requirements
prevented me from doing that in this case. Now FileMaker is showing
it's limitations and I might have the green light to replace it.
I'd like to use Obj-C/Cocoa.
So what's the "most Cocoa" client-server architecture?
This project isn't a huge database, it just runs a small company,
but it needs some features on the server beyond what I could do
with just MySQL, like emailing, faxing, logging, backups, etc. I'd
also like to do searches on the server to limit network traffic.
What I'd really like to do is develop the server using CoreData and
hook into OS X for faxing and authentication. I know CoreData isn't
designed to be multi-user, but is there a way to work around that?
Maybe with distributed objcts? If not, then that brings up
WebObjects. I don't know much about WO, but I think if I'm going to
do Java then I'd just use the open source projects I'm used to.
What do I do with the client though? Pretty much, I don't care what
the transport is, I don't want to have to worry about it. I do want
to use bindings on the client. That's why distributed objects is
appealing.
Anyway, it just doesn't seem clear what the endorsed client-server
strategy is at the moment. Any suggestions would help a lot.
Thanks,
Justin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden