Re: OS + iOS best practice
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/6/11 10:51 PM, Amy Gibbs wrote: After the announcements about iCloud, should I just wait a while and I'll be able to build this in 'for free' (there will be a cocoa way to do this)? While the iCloud announcement was obviously public, all the implementation details are under NDA (and of course, like other such subjects, cannot be discussed on this list). I presume, though, that you are an iOS program member; login to the dev center and you can read any pertinent documentation to your heart's content. (There are also NDA-cleared forums on the dev site you can use.) - -- Conrad Shultz Synthetiq Solutions www.synthetiqsolutions.com -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3tx8wACgkQaOlrz5+0JdWkagCfYtgxpBEUO4/QlR/Rb7i8flim XqIAn3sC0x2oerMXa2GD8kokFnJ6j8yX =5khG -END PGP SIGNATURE- ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
After the announcements about iCloud, should I just wait a while and I'll be able to build this in 'for free' (there will be a cocoa way to do this)? On 3 Jun 2011, at 9:29PM, Evadne Wu wrote: As for the SQLite file, I am never sure if Core Data’s OS X implementation and iOS implementation share the same format and will continue to be so, and it is surely a very strong and valid idea to just use an intermediate format you control, I’ve been bouncing them across OS X iOS with no problem… Note that Dropbox exposes directory hashes, so that might help with images. I’m not sure if referenced images would be updated at all — this can be a big problem if they can be updated outside the app and you need to handle that. For the record, going with Dropbox might not be very safe, could be not scalable at all, and might have security implications as Jeffrey pointed out. But it might work very well for your scenario. If you’re serious about making it robust, I still recommend that you create a tiny and dedicated web service for this app… -ev On Jun 4, 2011, at 04:23, Amy Gibbs wrote: Thanks Sounds like dropbox would be a good fit, I'll download the ask and give it a go. My current mac app stores the data in a sqllite file that I'm hoping to just sync with dropbox. However it does currently also store images in a directory and just store the paths as string attributes. Not sure of the best solution for those. I'm not expecting to always have web access on the iPad when the app is running. The images would not change too often once the app is initialised with data. A dozen or so new ones a month, and from the iPad they would only need to be read. Perhaps I could store the SQLite file and the images in a directory that can be stored in the dropbox directory? Many thanks for all your help. Sent from my iPad On 3 Jun 2011, at 19:48, Evadne Wu e...@monoceroi.com wrote: Dropbox sync is good for a pile of files, but no more than that. Let’s rebound the requirements: * there’s a single user Core Data app * want an iPad version of the app * the two versions will sync up Given the requirements, and add the fact that I’m pretty sure that Dropbox would keep conflicted copies of any file around, so there is no fear for lost data, and you can probably merge anything… it’s probably a good fit. If you don’t pull in any external resources, for example pictures on the filesystem which are only referenced by path strings in Core Data entities, the only thing that needs syncing would be the .sqlite file and things can probably work. If this is not the case then a simple Web service would go a long way. Dropbox carries its own stateless JSON based API, but there is a SDK out there (for prototyping purposes) too. -ev On Jun 4, 2011, at 02:16, Amy Heavey wrote: Thanks, It's an app for just me really. I just prefer to work on a desktop mac when I'm in the house, and I can't carry my iMac with me :) I do find typing much easier on an actual keyboard. Maybe I should just get a keyboard for the iPad? Many Thanks Amy On 3 Jun 2011, at 7:11PM, John Joyce wrote: On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/ev%40monoceroi.com This email sent to e...@monoceroi.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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:
Re: OS + iOS best practice
On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database.___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
Thanks, It's an app for just me really. I just prefer to work on a desktop mac when I'm in the house, and I can't carry my iMac with me :) I do find typing much easier on an actual keyboard. Maybe I should just get a keyboard for the iPad? Many Thanks Amy On 3 Jun 2011, at 7:11PM, John Joyce wrote: On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
Could indeed be easiest solution ;) You could also look at how you serialize or save data for export / import between two environments. Just have it custom save out to a standard plist format or a simple xml schema. Then you can decouple that from the CoreData versioning and differences. Internally, for speed or what have you it could easily import to the CoreData model. However, a simple web app might be just as feasible. Depends on what interests you at this point. On Jun 3, 2011, at 1:16 PM, Amy Heavey wrote: Thanks, It's an app for just me really. I just prefer to work on a desktop mac when I'm in the house, and I can't carry my iMac with me :) I do find typing much easier on an actual keyboard. Maybe I should just get a keyboard for the iPad? Many Thanks Amy On 3 Jun 2011, at 7:11PM, John Joyce wrote: On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
On Jun 3, 2011, at 11:04 AM, Amy Heavey wrote: I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. Yup. In fact I would try to share all of the model-related code between the two apps, to ensure that all the ‘business logic’ [I hate that word] is consistent. The easiest way to share the data is to use the file transfer feature of iOS 4, which will let you clumsily use iTunes to copy files to and from the iPad. It looks really simple to implement — IIRC most of it is just declaring in your Info.plist that you support the feature, and then specifying a subfolder of your Documents folder where copied files will live. Dropbox sync is a lot smoother, of course. I am not sure if there is a convenient Cocoa library to use for that. Coding it yourself probably isn’t too hard if you know your way around NSURLConnection, especially if you want to ignore niceties like the ability to browse folders in the dropbox. In the long run this will be an excellent use case for CouchDB (a document-oriented data store that excels at syncing), but the iOS version of that is still very much beta, and there’s no high-level API for it yet that gives you anywhere near the convenience of CoreData. [I’m starting to design one, though…] —Jens smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
Dropbox sync is good for a pile of files, but no more than that. Let’s rebound the requirements: * there’s a single user Core Data app * want an iPad version of the app * the two versions will sync up Given the requirements, and add the fact that I’m pretty sure that Dropbox would keep conflicted copies of any file around, so there is no fear for lost data, and you can probably merge anything… it’s probably a good fit. If you don’t pull in any external resources, for example pictures on the filesystem which are only referenced by path strings in Core Data entities, the only thing that needs syncing would be the .sqlite file and things can probably work. If this is not the case then a simple Web service would go a long way. Dropbox carries its own stateless JSON based API, but there is a SDK out there (for prototyping purposes) too. -ev On Jun 4, 2011, at 02:16, Amy Heavey wrote: Thanks, It's an app for just me really. I just prefer to work on a desktop mac when I'm in the house, and I can't carry my iMac with me :) I do find typing much easier on an actual keyboard. Maybe I should just get a keyboard for the iPad? Many Thanks Amy On 3 Jun 2011, at 7:11PM, John Joyce wrote: On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/ev%40monoceroi.com This email sent to e...@monoceroi.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
On Fri, Jun 3, 2011 at 2:48 PM, Evadne Wu e...@monoceroi.com wrote: Dropbox sync is good for a pile of files, but no more than that. Let’s rebound the requirements: * there’s a single user Core Data app * want an iPad version of the app * the two versions will sync up Given the requirements, and add the fact that I’m pretty sure that Dropbox would keep conflicted copies of any file around, so there is no fear for lost data, and you can probably merge anything… it’s probably a good fit. If you don’t pull in any external resources, for example pictures on the filesystem which are only referenced by path strings in Core Data entities, the only thing that needs syncing would be the .sqlite file and things can probably work. If this is not the case then a simple Web service would go a long way. Dropbox carries its own stateless JSON based API, but there is a SDK out there (for prototyping purposes) too. Be careful of Dropbox. The service encrypts data at its leisure and pleasure. With the laxed practices, I imagine they are more than happy to share with law enforcement on a whim rather than court order [2]. Jeff [1] http://seclists.org/funsec/2011/q2/135 [2] http://www.pcworld.com/article/225549/update_dropbox_will_hand_over_your_files_to_the_feds_if_asked.html ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
Thanks Sounds like dropbox would be a good fit, I'll download the ask and give it a go. My current mac app stores the data in a sqllite file that I'm hoping to just sync with dropbox. However it does currently also store images in a directory and just store the paths as string attributes. Not sure of the best solution for those. I'm not expecting to always have web access on the iPad when the app is running. The images would not change too often once the app is initialised with data. A dozen or so new ones a month, and from the iPad they would only need to be read. Perhaps I could store the SQLite file and the images in a directory that can be stored in the dropbox directory? Many thanks for all your help. Sent from my iPad On 3 Jun 2011, at 19:48, Evadne Wu e...@monoceroi.com wrote: Dropbox sync is good for a pile of files, but no more than that. Let’s rebound the requirements: * there’s a single user Core Data app * want an iPad version of the app * the two versions will sync up Given the requirements, and add the fact that I’m pretty sure that Dropbox would keep conflicted copies of any file around, so there is no fear for lost data, and you can probably merge anything… it’s probably a good fit. If you don’t pull in any external resources, for example pictures on the filesystem which are only referenced by path strings in Core Data entities, the only thing that needs syncing would be the .sqlite file and things can probably work. If this is not the case then a simple Web service would go a long way. Dropbox carries its own stateless JSON based API, but there is a SDK out there (for prototyping purposes) too. -ev On Jun 4, 2011, at 02:16, Amy Heavey wrote: Thanks, It's an app for just me really. I just prefer to work on a desktop mac when I'm in the house, and I can't carry my iMac with me :) I do find typing much easier on an actual keyboard. Maybe I should just get a keyboard for the iPad? Many Thanks Amy On 3 Jun 2011, at 7:11PM, John Joyce wrote: On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/ev%40monoceroi.com This email sent to e...@monoceroi.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/home%40willowtreecrafts.co.uk This email sent to h...@willowtreecrafts.co.uk ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
Re: OS + iOS best practice
As for the SQLite file, I am never sure if Core Data’s OS X implementation and iOS implementation share the same format and will continue to be so, and it is surely a very strong and valid idea to just use an intermediate format you control, I’ve been bouncing them across OS X iOS with no problem… Note that Dropbox exposes directory hashes, so that might help with images. I’m not sure if referenced images would be updated at all — this can be a big problem if they can be updated outside the app and you need to handle that. For the record, going with Dropbox might not be very safe, could be not scalable at all, and might have security implications as Jeffrey pointed out. But it might work very well for your scenario. If you’re serious about making it robust, I still recommend that you create a tiny and dedicated web service for this app… -ev On Jun 4, 2011, at 04:23, Amy Gibbs wrote: Thanks Sounds like dropbox would be a good fit, I'll download the ask and give it a go. My current mac app stores the data in a sqllite file that I'm hoping to just sync with dropbox. However it does currently also store images in a directory and just store the paths as string attributes. Not sure of the best solution for those. I'm not expecting to always have web access on the iPad when the app is running. The images would not change too often once the app is initialised with data. A dozen or so new ones a month, and from the iPad they would only need to be read. Perhaps I could store the SQLite file and the images in a directory that can be stored in the dropbox directory? Many thanks for all your help. Sent from my iPad On 3 Jun 2011, at 19:48, Evadne Wu e...@monoceroi.com wrote: Dropbox sync is good for a pile of files, but no more than that. Let’s rebound the requirements: * there’s a single user Core Data app * want an iPad version of the app * the two versions will sync up Given the requirements, and add the fact that I’m pretty sure that Dropbox would keep conflicted copies of any file around, so there is no fear for lost data, and you can probably merge anything… it’s probably a good fit. If you don’t pull in any external resources, for example pictures on the filesystem which are only referenced by path strings in Core Data entities, the only thing that needs syncing would be the .sqlite file and things can probably work. If this is not the case then a simple Web service would go a long way. Dropbox carries its own stateless JSON based API, but there is a SDK out there (for prototyping purposes) too. -ev On Jun 4, 2011, at 02:16, Amy Heavey wrote: Thanks, It's an app for just me really. I just prefer to work on a desktop mac when I'm in the house, and I can't carry my iMac with me :) I do find typing much easier on an actual keyboard. Maybe I should just get a keyboard for the iPad? Many Thanks Amy On 3 Jun 2011, at 7:11PM, John Joyce wrote: On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote: I hope this appropriate for this list, if not please accept my apologies. I've got a fairly basic core data app that I've written for personal use on my iMac. I'd like to have an iPad version as it would be very useful to have whilst I was mobile. (It's basically a customer/product database). Is there a best way to manage sharing the data between an OS and iOS version? I assume it will be possible as long as they use the same datamodel. I was thinking maybe some kind of dropbox sync would be best as it wouldn't depend on a network connection, and I wouldn't need to use both the mac an iPad versions at the same time. I have absolutely no idea how to do this though. I know some apps have built in dropbox sync but I fear it may be beyond me as I haven't found a handy tutorial anywhere. Can anyone point me in the right direction at all? Many Thanks Amy If it's an app for multiple users to have the same data, you probably want to have a central database that client apps retrieve data from. Core data isn't really a multi-cient database. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/ev%40monoceroi.com This email sent to e...@monoceroi.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/home%40willowtreecrafts.co.uk This email sent to h...@willowtreecrafts.co.uk
Re: OS + iOS best practice
On Jun 3, 2011, at 1:29 PM, Evadne Wu wrote: As for the SQLite file, I am never sure if Core Data’s OS X implementation and iOS implementation share the same format and will continue to be so SQLite’s file format is 100% consistent cross-platform. And I have no reason to think the same’s not true of CoreData’s schema, since it’s supposed to be compatible between OS’s. Note that Dropbox exposes directory hashes, so that might help with images. I’m not sure if referenced images would be updated at all — this can be a big problem if they can be updated outside the app and you need to handle that. If you make the application’s store a directory and put the images in it as well as the CoreData file, and if you sync the whole directory with Dropbox, it should Just Work. For the record, going with Dropbox might not be very safe, could be not scalable at all, and might have security implications as Jeffrey pointed out. Dropbox has been quite safe and scalable in my experience. I’ve been using it for a lot of my data for two years, have never lost data or gotten files messed up, and I can’t think of the last time it didn’t sync in a timely manner. The security issues are overblown due to the recent fracas. Yes, your files could theoretically be accessed by their employees or requested by the FBI. The same thing is true of your email, your iDisk, your Google Docs/Sites/Spreadsheets, any software running on your hosted web space, and anything else you put up in “the Cloud”. If you’re super paranoid you can encrypt and decrypt the files locally; but then you run into the complications of key management and transfer … which is one of the reasons cloud services don’t go as far as to do this. But it might work very well for your scenario. If you’re serious about making it robust, I still recommend that you create a tiny and dedicated web service for this app… I understand your point, but in practice, a service designed and run by professionals is going to be more reliable than a quickie web-app cobbled together in your spare time. (What’s the least reliable blog site I’ve ever used? The private WordPress installation I run on my domain. Mostly because the @*%$ sysadmin [me] never has the time to upgrade or fix it…) —Jens smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
