Hi Shameera,
> I have mentioned two approaches in my proposal [8] which we can use in > client side (see second last para of 2.2 section). After some discussions, > we (me and my mentor Lahiru) have agreed to use second approach which is, > write a new JSON client API using JavaScript. This makes life easy to > Front-End developers. They can use relevant API to retrieve and store data > to registry and communicate with other Back-End components like workflow > interpreter. > That means we would have a native JS Airavata API?. 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. > Another requirement is to support Danushka's AMQP implementation with > Rabbitmq for messaging. As I can see there is no any client available for > JavaScript in Rabbitmq client doc [9], But found this "rabbitmq + node.js = > rabbit.js" [10]. Danushka i would like to request your help on this, Can we > use this to consume rabbitmq queues? > If our model is going to be what I have explained above, then there will be no need for a RabbitMQ JS API. Thanks, Danushka
