Hi David,
two questions:
Why would you limit this to the sub domain?
Am I right in assuming that I could implement such a resolver and add it
to the resolvers in assembly/profiler.xml?
Thanks,
Frank
David Sean Taylor wrote:
Bhaskar wrote:
Hi David,
Can you bit explain, how this mapping to be done, like
http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
I looked at the documentation, didn't get it through.
This mapping does not currently exist. I was proposing writing and
contributing a new profile resolver based on the host string.
The idea is we would have a new profiling rule that used this resolver
as its first criteria. It could parse the host up, find the substring
up to the first ".", and use that to map to a subsite. Thus all
requests going to employees.* would then map to the "employee" subsite.
I would combine this with role-based declarative security, so that
customers would get access denied exceptions if they tried to access a
URL for employees, for example.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
