-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Markus,
Markus Strickler wrote:
>>Having only one repository for any site should always be the preferred
>>solution. If there is no solution in Magnolia, you can achieve the
> Hm, yes I liked the idea.
> Only question is, will magnloia support multiple website repositories in a
> single instance.
> And if it does, how?
I think the question is not the number of repositories, but the
addressing scheme for the content. For your application you need to
share the same "external name space" for different internal names.
>>desired behaviour using Apache mod_rewrite with mod_proxy
>>(for incoming
>>requests) and mod_proxy_html (for link rewriting).
> Hm, sounds interesting.
> Still I don't exactly like the idea to parse and modify the whole document
> before it gets posted. Sounds slow, and probably won't
> work with magnolias precompressed cached pages.
Precompressed pages: I have not checked this yet. But you could switch
off this feature and use mod_deflate instead. But parsing each page of
course causes performance drawbacks. The other problem is that your HTML
code needs to be clean, else pages will be corrupted afterwards.
An option for URL rewriting within Mangolia would be the best way, of
course.
> Do you know if mod_proxy_html works together with mod_cache?
I suppose yes, because mod_proxy_html acts as an extension for
mod_cache, but I haven't done any tests on this.
- --
Greetings,
|<laus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDPCdpf8QelBDGPp0RAmvMAJ0f3L8IHicZpnfB6RuYY9pFSnc1yACdFgSV
17hwNqrGKmju8rAZ0MhV6SY=
=ogPC
-----END PGP SIGNATURE-----
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
