On Tue, 7 Aug 2007, Kore Nordmann wrote: > 1) Indication of supported mechanism in backend handlers.
If you mean the capabilities with this, I think the interface parts are not going to work here - and making empty interfaces just sounds strange. So I would go for option 3: bitfield. > 2) Selection of best transport handler for requesting client. In your example code I see that the user has to register the transports - just like with the Document design I don't think users should generally be bothered with this. So for the default supported clients we should pre-register them. As for the canParse() bit - I think that would be better then just a regular expression. The Feed (hehe) component does do something similar. regards, Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
