Hi Holger,
well, I was going to propose dynamic library loading. But you beat me to
it. Guess it won't work. (Personally, I'm quite happy keeping the CGI
overhead low and using /Core. What's more, I use /Core most of the time
anyway. Haven't even installed the extended expiration version of /View
yet. But that's not to say that I'm not interested in /View. /Core is
just a better fit for what I'm currently doing).
Take Care,
Elan
Holger Kruse wrote:
[..]
> It would be possible to work around this by using dynamic library loading and
> linking, but that creates a flurry of other problems (compatibility, versioning
> etc.), so we would rather not do it. The best solution is to keep Core and
> View separate.
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
