[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] [RS Issue] 1.8.1 Registry Clients, line 520 needs clarification
Hi Farrukh, I still think that it is the Registry server's Web tier but let's get over it. A terminology differences in our views of the clients and servers won't make any big change here and it won't affect anybody. Thanks for the new Registry Client paragraph. I am OK with it. Regards, Goran ----- Original Message ----- From: "Farrukh Najmi" <Farrukh.Najmi@Sun.COM> To: <regrep@lists.oasis-open.org> Sent: Monday, January 24, 2005 9:08 AM Subject: Re: [regrep] [RS Issue] 1.8.1 Registry Clients, line 520 needs clarification > Goran Zugic wrote: > >> Hi Farrukh, >> >> I think that this is just terminology. In a multi-tier J2EE architecture >> your JSP/Servlet UI implementation is a part of the Web tier (you need a >> Web container to run JSPs and Servlets) which should formally be on the >> Registry server side. It could be on the same machine (application >> server) where your Registry application tier is running or it could be on >> a separate machine (your case) but to me it is still Registry server. I >> guess the reason why you put the UI on that "Registry Client" was to >> separate presentation layer processing from the application tier. Your >> case is not a special case to me. Your JSP/Servlet UI implementation is a >> standard Web tier implementation that separates presentation layer from >> the application logic and I don't see a reason for adding that "A special >> type of Registry Client" paragraph. I hope that I haven't misunderstood >> your implementation case. > > I would put it differently. In my mind, the definition of a registry > client is that it "is a software program that interacts with the registry > using registry protocols." > By that definition a server side web tier program that accesses the > registry using registry protocols is a registry client. > > I have replaced the text as follows: > " > 1.7.1 Registry Clients > > A Registry Client is a software program that interacts with the registry > using registry protocols. The Registry Client MAY be a Graphical User > Interface (GUI), software service or agent. The Registry Client typically > accesses the registry using SOAP 1.1 with Attachments [SwA] protocol. > > A Registry Client may run on a client machine or may be a web tier service > running on a server and may accessed by a web browser. In either case the > Registry Client interacts with the registry using registry protocols. > > " > > Let me know if this is adequate resolution of the issue. > >> >> Regards, >> Goran >> >> ----- Original Message ----- From: "Farrukh Najmi" >> <Farrukh.Najmi@Sun.COM> >> To: <regrep@lists.oasis-open.org> >> Sent: Sunday, January 23, 2005 3:17 PM >> Subject: [regrep] [RS Issue] 1.8.1 Registry Clients, line 520 needs >> clarification >> >> >>> Goran Zugic wrote: >>> >>> >>>> I told you that I will clarify my comment on "1.8.1 Registry Clients" >>>> second paragraph line 520: >>>> "... >>>> A special type of Registry Client is a Web Browser that typically >>>> accesses the registry using the HTTP 1.1 protocol. Note that it is >>>> possible for a Web Browser to access a service that is a Registry >>>> Client (not shown in figure) as is the case in a thin-client GUI. >>>> ..." >>>> What this paragraph says is that a Web Browser (that is a Registry >>>> Client) can access another Registry Client (Line 521). To me it could >>>> access Registry Server only. This sounds like we can have a case where >>>> a Registry Client serves as a Registry Server or as an intermediate >>>> point between the Web Browser and Registry Server. Is it possible? >>>> >>> >>> What I had in mind was something that reflected the case (we have such a >>> case in freebXML Registry implementation) where a web browser is used to >>> access a JSP/Servlet based web based User Interface (thin UI). The thin >>> UI is the actual Registry Client and talks to the registry interfaces >>> using SOAP over HTTP or HTTP/S. >>> >>> Maybe in that case it is misleading to call the Web Browser a Registry >>> Client? How should we capture the case I am trying to convey? >>> >>> -- >>> Regards, >>> Farrukh >>> >>> >>> >>> To unsubscribe from this mailing list (and be removed from the roster of >>> the OASIS TC), go to >>> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php. >>> >>> >> >> >> To unsubscribe from this mailing list (and be removed from the roster of >> the OASIS TC), go to >> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php. >> > > > -- > Regards, > Farrukh > > > To unsubscribe from this mailing list (and be removed from the roster of > the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]