PlainNote Progresses

Work on PlainNote is continuing. Eventually it will hopefully turn into the PlainNote ecosystem. I’m currently working on a sync library to sync up with a server that doesn’t exist yet. The server side is going to get some help from @funkatron. We have been collaborating on a google doc for the API.


Notable Items about the API

• Try to be RESTful, but don’t get stupid about it
  
• JSON is much better than XML, so only support JSON initially
  
• This needs to be open and hostable by others, so don’t use closed-source tech to power it
  
• If we’re worried about security at all, we should probably run this over SSL, since we’re sending account identifiers. That does make the backend stuff a little more complex, but doable. I wouldn’t worry about it at first.
  

Current Methods include

• login
• all (get all notes from the server)
• list (get an abbreviated list of notes from the server)
• one (get one note from the server)
• update (update a single note on the server)
• updatemany (update several notes on the server <future>)
• delete (delete a note from the server)

In the interest of being open I thought I’d get some information out there on what we’re working on. The ultimate hope would be to have the ability to view and edit notes across any device as well as the web and have it all play nice together. There are a lot of timing issues to think about as far as updates on multiple devices without sync. For simplicities sake I think our current direction is going to be take the latest edit as master and not try to merge.



Good things to come shortly…. (like the below WebOS version of PlainNote)