Josh,
> Unfortunately, the other key piece of information I have left out is that I > also need to tie into some C based APIs in order to drive some large Sun > robotic tape libraries. I also wish to achieve as high a degree of > concurrency as possible in the file moving/compression processes, and am > hoping to take advantage of the newer concurrent technologies that accompany > OS 10.6. Well... That's a good enough reason. Driving that Sun stuff through exec() and command-line utilities should be extremely painful and hard to maintain in the future. Do you really need to use MySQL -- or any other full-fledged RDBMS? I am not sure how big will be your dataset, how often it will be updated and how many users you'll have, so I can't help that much. I've heard of projects using a CoreData app as a server, and it doesn't seem to be that difficult to implement. You could make this server app expose a SOAP service that your web app (or any other client) could use so. If you ever need to develop a client for Windows, Linux or whatever, it would be much simpler, but it does seem to be the case. I've heard that Core Data is very scalable if you use the SQLite store. Maybe you should give it a try. If you really need an RDBMS, you could consider PostgreSQL and the BaseTen framework (basetenframework.org). It feels a lot like Core Data, but for Postgres. > Should prove to be fun (or at least very interesting...) Why do we, developers, love challenges? ;) Cheers, Flavio_______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
