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

* Your Email Address
* Spam protection	Enter the letters below: \ /. .___. .\ / >< \| [__ \|\ \| >< / \\|___[___\| \\|/ \
Comment	>>> If you still rely on the external API methods defined for Trean > >>> instead of calling the Trean API directly in json.php, would it make > >>> more sense to add a generic JSON backend to Horde's RPC library? > >> > >> It would. I had a reason for deciding against implementing JSON-RPC > >> (pretty much the only RPC-over-JSON standard I saw.) > >> (http://json-rpc.org/wiki/specification) Now I'm not sure why, but I > >> think it may be that the newest version is still being written up in > >> specification. I'll look at it some more. > > > > The spec looks good. > > > >>> Regarding the AJAX and JSON stuff inside the XPI, I suggest that you > >>> use prototype that we use anywhere else in Horde. The most recent > >>> version has support for a CSRF protection built in. > >>> Heck, we could even build the XPI on the fly including the source > >>> files directly. Much easier than rebuilding the XPI anytime you > >>> change something. I plan to do this for IMP since ages. > >> > >> This sounds like a good idea to look into. Where is the source? > > > > In my head. But it shouldn't be too hard. We have the Horde_Compress > library that we already use to create ZIP files on the fly. We should > probably put the XPI contents under trean/lib/XPI or > trean/templates/xpi with the same layout like in the XPI file, for > better maintainability. > > > >> P.S. Today was my last day of high school, woohoo! And I'll even > >> have a week that will be pretty open for working on this ;) > > > > Congrats! Good for us, I guess.
Attachment
Watch this ticket

Saved Queries