Return-Path: X-Original-To: apmail-oodt-dev-archive@www.apache.org Delivered-To: apmail-oodt-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 453D618DCB for ; Sat, 20 Jun 2015 00:41:33 +0000 (UTC) Received: (qmail 51779 invoked by uid 500); 20 Jun 2015 00:41:33 -0000 Delivered-To: apmail-oodt-dev-archive@oodt.apache.org Received: (qmail 51743 invoked by uid 500); 20 Jun 2015 00:41:33 -0000 Mailing-List: contact dev-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@oodt.apache.org Delivered-To: mailing list dev@oodt.apache.org Received: (qmail 51731 invoked by uid 99); 20 Jun 2015 00:41:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Jun 2015 00:41:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lewis.mcgibbney@gmail.com designates 209.85.213.176 as permitted sender) Received: from [209.85.213.176] (HELO mail-ig0-f176.google.com) (209.85.213.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Jun 2015 00:39:17 +0000 Received: by igbiq7 with SMTP id iq7so24966880igb.1 for ; Fri, 19 Jun 2015 17:41:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=URbq2ckUfc36QraMuV392kyhox2GrxI7EZFnG0ObL1I=; b=IZG77KmfPUEQfIHjGU9PHZJOwVuS3o0FSxapRrcwzoXRv3xVoLocmhPELzcLKgJS90 o606qZHvUcdkV9KwJsx+/ODD6KSrVMaL3vhP2qQfbI2Qj5sUGkRNUK+xvtlfIKF/Uiaz Jsrb6UacqEJuFha+DqbR6gLBwLLW38X2qDtylyY7U15YEK14LgZbmgm295xhf+rKDMvM WwfV2XAxuWg2NyI5+L4v0bnx17MegRJN3ywj+OChH5yXBCZ5u5rKpg0bn5D5cdcx+8rg SsC7BDqEwoPmC2kFFBefvvXPhM1Hxyu22Ugj6+UCy6DzrKclX/DIG21cKUzgnB83NY/F J7/g== MIME-Version: 1.0 X-Received: by 10.43.163.129 with SMTP id mo1mr14473605icc.61.1434760864977; Fri, 19 Jun 2015 17:41:04 -0700 (PDT) Received: by 10.36.39.196 with HTTP; Fri, 19 Jun 2015 17:41:04 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jun 2015 17:41:04 -0700 Message-ID: Subject: Re: GSoC - Week 2 From: Lewis John Mcgibbney To: Radu Manole Cc: "dev@oodt.apache.org" Content-Type: multipart/alternative; boundary=001a11c30b4eb1dc1c0518e84b82 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c30b4eb1dc1c0518e84b82 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Your class diagrams look dynamite. Thanks for the update. Have a great weekend. Lewis On Friday, June 19, 2015, Radu Manole wrote: > Hi, > I uploaded UML diagrams for the rest of the classes. > The predominant similarities are: > - In most cases, the client doesn=E2=80=99t have a additional logic from = its > ability to remotely call methods, and where it is it can be separated. > - classes share a lot of similarities that they can be abstracted using > the same similar method used in catalog module creating objects using > factory. > Thanks. > > 2015-06-17 0:05 GMT+03:00 Lewis John Mcgibbney >: > >> Hi Radu, >> >> On Tue, Jun 16, 2015 at 1:42 PM, Radu Manole > > wrote: >> >>> >>> I tried adding a UML diagram on the wiki >>> https://cwiki.apache.org/confluence/display/OODT/XMLRPC+uses >>> Although I didn't generate it, but created it by hand. >>> Any feedback is appreciated. >>> >> >> I've formatted and added feedback on there. Nice work. >> >> >>> >>> I can see some similarities in the uses, but I didn't yet write a >>> proposal for separating XMLRPC from the code. >>> >> >> OK, what are the similarities? >> >> >>> The most confusing part is the ExecServer. If someone can give some >>> details for what is used, it would be great. >>> >> >> First, I would ask you to use one of the IntelliJ or Astah tools to >> generate class diagrams for all aspects of the OODT projects which inclu= de >> XMLRPC functionality. This way the structure and communication is explic= it. >> Once you've done this, please reply to this thread and we can forward th= e >> conversation. >> >> >>> And one more question related to it "can't find anywhere is the OODT >>> code that the callLocalServerManager method be called". >>> >>> >>> Neither can I right now. For the time being please progress with the >> class diagrams as described above. I will keep searching for this and we >> can touch base here once we've located it. >> Thanks >> Lewis >> >> > > --=20 *Lewis* --001a11c30b4eb1dc1c0518e84b82--