Tickets :: Comment on [#2565] Firefox 3 bookmarks extension

* Your Email Address
* Spam protection	Enter the letters below: _ _ _______ ________ __ \| \ \| \| __ \ \ / / _ \ \ / / \| \\| \| \|__) \ \ / /\| \|_) \ V / \| . ` \| ___/ \ \/ / \| _ < > < \| \|\ \| \| \ / \| \|_) / . \ \|_\| \_\|_\| \/ \|____/_/ \_\
Comment	>>> - For other ways to do it than xmlrpc struts, it depends what you > >>> want to work with on the browser side. We have the beginnings of > >>> RSS/Atom feeds for Trean; if this extension could use that data that > >>> would definitely simplify things. Another possibility is to use json > >>> instead of xml-rpc; that data could be requested directly from Trean > >>> and would be much smaller than XML. And could just be eval'd (after > >>> stripping a necessary security delimiter) on the javascript side. > >> > >> Yeah, I thought about json afterwards. Perhaps that would be much > >> more efficient and simple. It might also make sense to leverage the > >> existing RSS stuff, yeah. My only problem is wondering if it makes > >> sense to have separate download/upload mechanisms. (Though I think > >> RSS or Atom has a publication mechanism as well, which could be used > >> for uploading.) > > > > Yes, Atom has a publication mechanism - we'd need to implement it, > but that'd be nice anyway. :) I think JSON is probably the way to go > for now for simplicity on both the Trean and Mozilla sides, but that > if Atom is easy to deal with on the Mozilla side we could move to > that easily, and perhaps sooner rather than later. > > > >> I should also note that the synchronization is > >> pretty primitive right now - limited to simply the existence of > >> bookmarks; it doesn't sync changes to URL and such. Perhaps another > >> protocol would better address more complete synchronization. What do > >> you think? > > > > Synchronization protocols are a tricky problem. We support SyncML in > other parts of Horde, and that'd be very complete, but we'd need a > full SyncML client in Mozilla, and that'd be a ton of work. I think a > relatively primitive mechanism is fine for now - especially if > creating/editing bookmarks are delegated to Trean. > > > >>> - What do you think about calling the menu item "Horde" so that > >>> perhaps in the future it could host other Horde features? Or should > >>> we keep things separated into other extensions? > >> > >> Renaming it sounds fine, but I'm wondering if the menu would become > >> too confusing if other features were integrated. > > > > You're probably right. > > > >>> One other question - the extension seems to have a persistent cache of > >>> credentials to log in to Horde. How is this handled? > >> > >> It's stored in the Password Manager (Tools -> Options -> Security -> > >> Show passwords), with a site of "treanmarksExtension." I stole the > >> idea from another online bookmarks extension. :-) > > > > Ah, nice. > > > >>> Last note for now - I committed several parts of your patch that made sense > >>> independently (at least, enough sense). > >> > >> OK. I hope they're still useful if the bookmark transfer mechanism > >> is switched. :-) > > > > Should be, they were related to the popup windows and such. > > > >> I'm fairly busy at the moment, but I'm hoping next week I can work on > >> these things more. In the meantime, I would appreciate peoples' > >> comments on RSS/JSON and perhaps the UI issues. > > > > Cool, looking forward to it.
Attachment
Watch this ticket