OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-comresolve message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [regrep-comresolve] Proposed resolution to 156 and 167


In my opinion, your reply does not state that the user can see the metadata
and issue the "get details" calls later so I do not see how his original
thread is a misunderstanding of the behavior as specified.  His
understanding and your reply appear to be virtually the same.  a
GetContentRequest message asks the QueryManager to resolve links and send
the content back in a payload.

Your reply to Duane was:

	A Registry client can issue a <GetContentRequest> to an 
	ebXML registry.  The request contains a collection of 
	<ObjectRef> elements each containing a UUID.

	The Query Manger interface take each UUID specified in the 
	request and uses it to resolve the link to the corresponding 
	repository item in the repository.

	It then fetches each repository item from the repository 
	and package each as an additional payload in the outgoing 
	response message. Note that no metadata is involved in this 
	operation other than the supplied ids.

	Finally, the QueryManager sends the response message back to the

Can the user simply issue a <getObject> or some equivalent that only returns
the <registryObject> metadata?  The client can then issue all of the
<getContentRequest> messages that he/she wants to.  Is this the simple
answer that Duane was really looking for?


-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
Sent: Monday, March 18, 2002 8:55 AM
To: Munter, Joel D
Cc: 'Oasis RR Comment Resolution'
Subject: Re: [regrep-comresolve] Proposed resolution to 156 and 167

Here is Duanes response:



As long as the user can select to return only the metadata,  then
manually retrieve each RegistryObject one at a time, much like a user of
a commercial HTML search engine, it should be fine from the users
persepective.  My feelign is that any time more than one result is
returned,  a human will likely be browsing the results.  An application
will be the user for more directed queries returning one or zero results

I am stil worried about the possibility of DOS type attacks but there
are other worries to figure out first.

<private thought unrelated to issues 156 and 167 snipped>


"Munter, Joel D" wrote:

> Thanks you.  Did Mr. Nickell reply?  Joel
> -----Original Message-----
> From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
> Sent: Monday, March 18, 2002 7:53 AM
> To: 'Oasis RR Comment Resolution'
> Subject: [regrep-comresolve] Proposed resolution to 156 and 167
> Attached is my private response to Duane. This is also the proposed
> resolution for the issues based on previous email discussions with the
> team prior to this alias being established.
> --
> Regards,
> Farrukh
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC