I'm building a webservice for plain text files at http://www.simpletext.ws. Since the site is restricked to text files it can be smart about updating them, in particular all updates are done by patching the files. This means that if a file is changed from multiple browser windows (or native clients) then in most cases the changes will all be merged together. If there is a conflic the site records that conflict so that the user can later manually resolve it. The code for the site is open source, and the site has a public API.
That's what I've built so far. The question that I'm currently working on is how to get that data from the website to desktop apps. The approach that I'm currently taking is to build that sync code directly into my apps (TaskPaper/ WriteRoom) and then they store the website file locally, and do some bookeeping in a hidden database. That approach is working, but it's messy and not very flexible. And now to my real question. Would MacFUSE work as an alternative approach? Could it be used to build a file system that was limited to text files only. And that was just a plain list of files with no directory structure? And that peridically synced changes with the website? If it could be made to work then MacFUSE looks like a neat approach, because it seems like I would be able to hide my bookeeping data so that it was invisible to the file system. It would also mean that any app could read/write my text files and stay synded, they would need to have the sync code built in. I'd love to hear what you think. Thanks, Jesse --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
