Hi Subho, Please find my comments inline.
On Mon, Jun 3, 2013 at 4:38 PM, Subho Banerjee <[email protected]> wrote: > Hi Shameera, > I am working on the sub-project of constructing a webapp to compose > workflows. I had a few questions, to ask you - > > I thought the protocol > > > conversion layer would bridge the existing API and JSON. In essence it > > > would accept input in JSON, call the API and return results in JSON. > > > > > > > This was the plan (This is suggested as the first approach in my > proposal), > > but to implement this we need to use java inside the JS. From developer > > perspective it is not a good idea as there are difficulties to debug and > > lack of tooling support. > > > > > ---> Are you making the changes so as to build a service that provides XML? > Or are you writing a front end client (a set of classes or methods in > Javascript) as well, which I will be calling. I will provide a JS client API. You can simply use that API to do the background works for you, Actually with this approach Front end development people don't need to think about this conversion as it will be handled by this new JS client. This is similar to the existing Airavata client API ( Note: may not be identical to that) but written in JS. In view of the above question > and snippet, what do you mean by using Java inside JS? > Another possible way to provide this feature (use JSON data format) is implement another Java Airavata Client interface which use JSON instead of XML. If we go with this approach, you have to call this Airavata Client API inside your JS code. That is what i mean by using Java inside JS. > > ---> I would personally prefer, if the JSON API that you design is as close > as possible to the current XML scheme. Maybe we can define a set of rules > as to how you will convert a XML message to JSON, in which case, I can then > work assuming that the frontend will get all messages from your service > with these rules applied. This will make it easier for us to > work independently in the beginning and then finally put everything > together as the data schema of the messages does not change, only the data > format. > Yes, You are more than welcome to propose any other conversion which you think more inline with existing XML schema than above conversion or any suggestion to improve above conversion. Cheers, Shameera. > > Cheers, > Subho. > -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
