On Mon, 2002-12-02 at 11:21, Nicola Ken Barozzi wrote: > Now it's time for some meat. > > This is how James uses the Context: > http://jakarta.apache.org/james/mailet/org/apache/mailet/MailetContext.html > > - What would data-only-usage Context advocates do with it? What problems > does it pose? > - Why is this (for method-containing Context advocates) the best solution? > - Why do I have a Context interface when in fact the Context is used > even without actually needing the specified method? > > If we don't discuss on real code, we won't get anywhere.
Apples 'n pears if you ask me. The JAMES MailetContext is not intimately related to the avalon Context at all. The MailetContext is used in a well-defined problem domain (e-mail; mailets), the avalon context is way more generic. If one were to refactor the mailet API to create a closer coupling between it and avalon framework, there's a lot of things to change. Stuff like log(), bounce(), store() and send() would not make sense in the scope of an avalon context. cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
