[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.technology.ohf] Re: XCA with NIST's public registry
Hi Matt,
So I was thinking to try this out, but my confusion is that I think a piece is missing. My understanding was that XCA looked something like this:
xds consumer -> XCA initiating gateway -> XCA receiving gateway 1
-> XCA receiving gateway 2
-> XCA receiving gateway n

The initiating gateway then gathers up the results from all the receiving gateways and returns it in one cohesive response to the xds consumer actor. So as I understand it the bridge would be acting as the xds consumer that knows how to talk to an XCA initiating gateway, right? However, NIST implements an XCA receiving gateway only- as far as I can see.

So we're missing the initiating gateway in any testing scenario involving NIST right? Or is the bridge sending the Cross Gateway Query and Cross Gateway Receive transactions directly?

thanks,
Jesse

Matthew Davis wrote:

Jesse,

The Bridge... not exactly tested on XCA yet. Ha ha. I'd like to spend some time in the next month playing with Bill's implementation, it would be good for the mind (and soul) for us to validate that the paradigms even come close to working. I think our friends at Sage or Wellogic tested XCA at HIMSS and it worked - but I'm sure it wasn't extensive.

I don't believe that a GetDocumentQuery in the Bridge can carry over the homeCommunityId yet. That's something that definitely needs to be added (something I totally forgot about). All other types of XCA should be supported - find documents query, retrieve document set - should work with XCA.

-Matt


Sarah Knoop wrote: 
Ah that list ----

Correct - no we have not tested with this -- but we can sure try. Second - the bridge does not implement either gateway so it needs to connect to an initiating gateway. We have XCA support (to the extent documented, ie management of the homeCommunityId) on our XDS.b consumer -- and I believe this is made invokable at the bridge level via the rhio config when you set an xca gateway id (and endpoints) for a rhio. Matt would have more insight - but I don't think, yet, we allow for a stored query to be directed at a gateway via the bridge. The retrive document set in the bridge uses the underlying java plugin algorithm that gives precidence to retriving the document set via the gateway, when this bit of information is present.

- Sarah



Jesse Pangburn wrote:
Hi Sarah,
If you mean NIST did not implement one at Connecathon, that's true. However, Bill has been working on a receiving gateway integrated with his registry. Are you on the ihe-xds-implementers google group? I've gotten the occasional posting about it on that list.

http://ihewiki.wustl.edu/wiki/index.php/XDS_Main_Page#Important_URLs_.2F__WS_Endpoints 
there's a link to the urls for the endpoints.

So in any case, it seems from your answer that no, you guys have not tested with it :-) Anyone else?

Is the bridge acting as an initiating gateway? Or does it need an initiating gateway to talk to which would then turn around and talk to NIST's receiving gateway?

thanks,
Jesse

Sarah Knoop wrote:

Good question ... To my knowledge, NIST did not implement an XCA Gateway, making it difficult for anyone to test an XCA-enabled XDS.b Consumer. The profile also faced a fair number of CPs this year around the expectations/handling of homeCommunityId - so that should shape things for this next round, albeit experimental - perhaps not so 'highly experimental' :-)


- Sarah 




Jesse Pangburn wrote:

Hi,
Have you guys tried the bridge XCA code with NIST's public registry? I have not yet but was curious if you guys had, or if there's been any work on it since the "highly experimental" stage it was in at US Connectathon 2008?

thanks,
Jesse