Hi there,
-----Mensagem original-----
De: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> Ok, this covers a lot of situations and imho too many :) I like it
> "simple". Perhaps my view of a lookup is too simple but I currently
> have two use cases:
> a) I want a component that provides service XY
> b) I want a specific (named) component that provides service XY
> The service is defined by a (Java) interface - so I think my use cases
> are covered with my simpler approach :)
>
> Can you give some use cases or scenarios where you need your version
> of a discovery strategy?
Hey, I'm not saying that we should use the ServiceTemplate strategy as it
is. But I'm saying that only a hint may not be enough :-)
Do you want use cases, uh? Hmmm..
Server side instant messaging application. As new versions of client
application are release there are a few differences implemented in the
protocol (and new features). After the registration, the server may ask
through lookup
LookupCriteria criteria = new LookupCriteria( ClientProtocolHandler.class );
criteria.add("protocol-version", "4.2.1.0");
criteria.add("firewalled", Boolean.FALSE );
WDYT?
Cheers,
hammett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Excalibur Project -- URL: http://excalibur.apache.org/
