On Wed, 2007-08-08 at 14:00 +0200, Derick Rethans wrote: > On Tue, 7 Aug 2007, Kore Nordmann wrote: > > 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.
As clarified in my follow up mail, a standard set of transport handlers is always registerd by default - you would just need to do this for custom handlers. I see a bit of a difference compared with feed, because I don't think you ever need more then the client name to decide which handler to use - and this spares us the loading of several classes on each request. -- Mit freundlichen Grüßen / Med vennlig hilsen Kore Nordmann (GPG: 0xDDC70BBB) eZ Components Developer eZ systems Headquaters tel +49 (0) 231-9742-7750 | fax +49 (0) 231-9742-7751 [EMAIL PROTECTED] | eZ systems | ez.no
signature.asc
Description: This is a digitally signed message part
-- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
