Hi Vijayendra, It should ideally go into common module IMO. Then the issue is that we need to use Airavata client API inside it, which might cause cyclic dependency clashes. We can have it as a separate module but I can hardly think of any protocol conversion other than XML <-> JSON.
Cheers, Danushka On Tue, Jun 25, 2013 at 12:01 AM, Vijayendra Grampurohit < [email protected]> wrote: > Hi Danushka > > This looks fine. But what if we have protocol (XML/JSON protocol conversion > module) > as a separate branch and not as a sub module under 1. web-gui > (xbaya-web-ui. > > Regards > Vijayendra > > > 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. > > > > 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 > > > > > > > > >
