[wsf-dev] ID-WSF Stack, starting point

Cahill, Conor P conor.p.cahill at intel.com
Fri Feb 9 11:03:22 EST 2007


 

> -----Original Message-----
> From: wsf-dev-bounces at openliberty.org 
> [mailto:wsf-dev-bounces at openliberty.org] On Behalf Of Scott Cantor
> Sent: Thursday, February 08, 2007 5:30 PM
> To: wsf-dev at openliberty.org
> Subject: Re: [wsf-dev] ID-WSF Stack, starting point
> 
> > 	For something like ID-WSF you have a stack along these lines:
> > 
> 
> Just for clarification, since that came out of a different 
> discussion context, things like the DS and AS are 
> applications in my terminology here.

They are in mine as well... Although I defined a class for 
instantiating a new service instance (the C++ object that 
I use to send liberty messages to a service) which took a 
service type as a parameter and did all the discovery
mumbo-jumbo to get the EPR for that service.

For the most part, I think our WSC library should hide the DS
from the WSC (and probably not even worry about the AS, given
that we want to bootstrap from an SSO session).

Conor


More information about the wsf-dev mailing list