Hi Danushaka, On Mon, Jun 24, 2013 at 11:47 PM, Danushka Menikkumbura < [email protected]> wrote:
> Hi Suresh, > > I think we need to have the following structure. > > 1. web-gui (xbaya-web-ui?) - The Web UI would be a top-level module, under > which we may have the following sub modules. > > - ui (Widgets, graph, canvases, etc) > - workflow (Workflow composition, execution) > - monitor (Workflow monitoring) > - protocol (XML/JSON protocol conversion module) > > 2. ws-messenger.client.protocol.amqp - AMQP client API bits > > 3. xbaya-gui.ui - AMQP configuration + monitoring. > +1 , But XML to JSON conversion is not with the front end. it happens in the backend(I will provide a diagram to explain this).What I provide is JS client API, therefore it would be good to have separate module name "client-api" for this. Thanks, Shameera. > > Sanchit, Shameera, Subho, Vijayendra and Viknes, what do you think?. > > Thanks, > Danushka > > > > On Sun, Jun 23, 2013 at 6:16 PM, Suresh Marru <[email protected]> wrote: > > > Hi All, > > > > Please discuss how should we structure the SVN repo for gsoc projects? > > certainly not by student since every one is contributing to master > project. > > So may be the functional components? > > > > I created a sandbox area, please discuss how individual modules should be > > organized and please create JIRA's and submit patches to this repo. > > > > https://svn.apache.org/repos/asf/airavata/sandbox/gsoc2013 > > > > Suresh > > > > > -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
