RE: Same Origin Policy JSONP *may* be worth a look at: http://bob.ippoli.to/archives/2005/12/05/remote-json-jsonp/
However do take heed of the security concerns as described here: http://en.wikipedia.org/wiki/JSONP Cheers, Antony On 30 April 2013 10:54, Antonia Horincar <[email protected]> wrote: > Can you tell me more about how the RestOnTracPlugin works, please? I > can't seem to find any documentation for this plugin. Do you have any > suggestions on how can it be used for this project? > Also, what other technologies do you suggest for this project so I can > have a closer look at them? > > Regards, > Antonia Horincar > > On Tue, Apr 30, 2013 at 10:35 AM, Joachim Dreimann > <[email protected]> wrote: > > On 30 April 2013 06:18, Olemis Lang <[email protected]> wrote: > > > >> On 4/29/13, Antonia Horincar <[email protected]> wrote: > >> > Hi, > >> > > >> > >> :) > >> > >> > I recently sent a message regarding the GSoC project on embedding > >> > Bloodhound tickets and objects. I have given some more thought on how > >> > to approach the project and my idea is using ajax to retrieve > >> > information about the objects through JSON, > >> > >> AFAICT , Ajax is problematic while embedding content in third-party > >> sites due to browser's same origin policy . > > > > > > ..if you're more interested in the Ajax side you could look at > introducing > > it to Bloodhound itself. > > > > I'm sure there is plenty you could achieve that would make a big impact > on > > the application from a user's perspective, like using Ajax to update > ticket > > pages, change history, activity feeds.. > > > >> and therefore create a > >> > JavaScript API for the client side and a JSON generator on the server > >> > side. > >> > > >> > >> FWIW , we have started a plugin (namely trackhacks:RestOnTracPlugin) > >> implementing Trac REST API on top of trachacks:XmlRpcPlugin > >> > > > > You're welcome to use plugins like this (and improve them if you need) to > > implement your project. > > > > > >> > >> -- > >> Regards, > >> > >> Olemis. > >> > >> Apache™ Bloodhound contributor > >> http://issues.apache.org/bloodhound > >> > >> Blog ES: http://simelo-es.blogspot.com/ > >> Blog EN: http://simelo-en.blogspot.com/ > >> > >> Featured article: > >> > > > > > > > > Hi, > >> My name is Antonia Horincar and I'm a student planning on applying for > >> the GSoC program. The project I am most interested in is Creating > >> embeddable tickets or objects for Bloodhound. > >> I would like to find out more details about the implementation of the > >> project (what features should the system have and what implementation > >> techniques would be most appropriate for this project), as I am > >> currently writing my proposal. Also, what is the suggested timeframe > >> for implementing the project? > > > > > >> Regards, > >> Antonia Horincar > > > > > > There is clear timeline defined by Google: > > June 17 - September 23 > > http://www.google-melange.com/gsoc/events/google/gsoc2013 > > > > There is some flexibility in how much time you spend per week on the > > project, but it should be your primary focus this summer: > > > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#11._How_much_time_is_required_to > > > > Cheers, > > Joe > > > > -- > > Joe Dreimann | *User Experience Designer* | WANdisco< > http://www.wandisco.com/> > > > > @jdreimann <https://twitter.com/jdreimann> >
