Vadim Gritsenko wrote:
>>From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>
> ...
>
>>You have simple sitemaps for simple problems and complex sitemaps for
>>complex problems.
>>
>>Remember, we have a wide range of needs. One sitemap is not going to
>>fit all needs.
>>
>
> ...
>
> Ok. Will this be an option (pluggable/configurable) or an optimization
> of the sitemap engine? In both cases, I don't mind if it does not breaks
> sitemap and provides speed up for some people out there.
This would be a *possibility* as a foundation for a new Sitemap syntax.
In the end, when we start compiling COcoon Blocks, we will have a highly
specialized sitemap that will allow us to perform all types of
optimizations that would otherwise be impossible with the current
general purpose sitemap.
Keep in mind, we have *several* components for Generators, Transformers,
Serializers, etc. We really only have one implementation for the
sitemap. I am advocating formalizing the contract of the Sitemap
(or Processor since that is what its interface is), so that we have
the possibility of comming up with a truly fast sitemap that is
specialized for our purposes.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
