From: "Joerg Pietschmann" <[EMAIL PROTECTED]>
> Jeremias Maerki <[EMAIL PROTECTED]> wrote:
> > By the way: What's the current agreement whether to use Avalon or not? I
> > mean, we're already using LogKit (which is cool).
>
> No, it's not cool unless done properly. I don't think users
> who want
Jeremias Maerki <[EMAIL PROTECTED]> wrote:
> By the way: What's the current agreement whether to use Avalon or not? I
> mean, we're already using LogKit (which is cool).
No, it's not cool unless done properly. I don't think users
who want only pure FO processing should be forced to use
another he
Keiron Liddle wrote:
[..]
> There are a number of packages in Avalon that would be useful, such as
> command line parsing.
> I would be for an integration in general espacially since cocoon uses it.
+1 Avalon sounds interesting (pooling etc.) but I did not have a
close look yet.
> There will
> Just as an idea: Have you looked at Avalon Excalibur's caching package?
> Pretty good stuff.
>
> By the way: What's the current agreement whether to use Avalon or not? I
> mean, we're already using LogKit (which is cool). On the other side, if
> we moved to the newer org.apache.avalon.framework
> Note: this is still in progress, input in the code is welcome. Needs
> documenting formats, testing. So all those people interested in images
> should get involved.
> Threading
Thanks for thinking about this!
> Caches
> --
>
> LRU
> All images are in a common cache regardless of co
Note: this is still in progress, input in the code is welcome. Needs
documenting formats, testing. So all those people interested in images
should get involved.
Images in FOP
-
Images may only be needed to be loaded when the image is rendered to the
output or to find the dimensio
