Portal : 2 Global Profiles depending on URI?

[Philippe Guillard <pg...@soociety.com>]

Hi all,

I'd like to use the same portal with 2 Global Profiles depending on URI
requested.

Lets say i have www.mysite.net and category.mysite.net, after
URLrewriting i could have www.mysite.net/potal/portal/1 and
www.mysite.net/portal/portal/2 that i'd like to render with
profile/layout1 and layout2.

I think about replacing portal pipeline with 
<map:match pattern="portal/*">, then use the parameter in

<layout-global-load
uri="cocoon:raw:/load-global-profile?profile=layout{1}"/> 

but don't know how to do this.

Anybody idea or other suggestion welcomed !!

Phil  


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

portal-many subdomains-vhosts

[Philippe Guillard <pg...@soociety.com>]

Hi all,

Hope somebody can give me hints/suggestions on this :

I plan to have many categories as subdomains, i need:
(abstracting all the virtual hosting or apache http mod_rewrite stuff)

http://myhost.mydomain.com/category1/portal
http://myhost.mydomain.com/category2/portal
...
http://myhost.mydomain.com/categoryN/portal

I use portal engine, coplets/profiles/users/roles are similar, but with
data relevant to the right category, say like Yahoo groups. I've found 2
ways to render this :

- use automount to mount as many sitemaps/folders as i have categories
and implement maybe as many portals in cocoon.xconf...I think this will
be far too heavy.
- from now i used redirects :

in samples/blocks/portal/stemap.xmap:

<map:match pattern="cat/*/**">     
<map:act type="session-propagator">
    <map:parameter name="cat" value="{1}"/>
</map:act>      
<map:redirect-to uri="cocoon:/{2}" session="yes"/>
</map:match> 

<map:match pattern="portal">  
<!-- all is the same here -->

and use session parameter "cat" to feed my coplets with relevant data

That way i can launch 
http://localhost:8888/samples/blocks/portal/cat/category1/portal
http://localhost:8888/samples/blocks/portal/cat/category2/portal
and stay artificially in the respective folder.

Not clean isn't it?
Problems are :
- Performance, not optimal for caching, i have many redirections... 
- I can't pass from category1 to category2 from URI part of the browser,
since cachingURI coplets need an event to refresh
- When the user logs in, i have new session object, i bypassed this by
putting the session parameter as hidden field in the login form and then
put it again in the session...I plan an action extracting the category
from requestURI and making it available to the pipeline. 

Any idea how to do this better? 

Regards,

Phil 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org