Re: URL pattern /admin/*

----- Original Message -----
From: "Christian Cryder" <[email protected]>
To: <[email protected]>
Sent: Wednesday, January 15, 2003 17:33
Subject: RE: [Barracuda] URL pattern /admin/*


> Hi Andras,
>
> Well, the way things are currently implemented, anything that ends with
> *.event gets routed to ApplicationGateway (which youy are seeing), and
> ApplicationGateway then tries to determine the event name. It does this
> first by looking at the servlet path info, and if that is null, then it
uses
> the actual URI name. In this case, the path is coming back as 'admin', and
> so Barracuda thinks that is the event name you are after (which it isn't).
>
> Before I venture a guess at possible solutions, can you give us soime
> insight into what you are trying to accomplish here? Why do you want to
use
> the /admin path to precede the actual event? Why not just use the event
> name? Or perhaps something like
> http://myhost/mywebapp/GetLogin.event?Admin=true
>
> Help us understand what you're after here...
>
> Thanks,
> Christian
> ----------------------------------------------
> Christian Cryder [[email protected]]
> Internet Architect, ATMReports.com
> Barracuda - http://barracuda.enhydra.org
> ----------------------------------------------
> "Coffee? I could quit anytime, just not today"
>

    Hi,

Thank you for answering.
So here is what i am trying to do, i have a webapp that has an admin part
and a public part. I want to separate these 2 parts as much as possible so i
have
different event.xml files, different application gateways etc.
Now one choice would be i guess to name the public events and admin events
differently like *.event and *.aevent   but i don't like this solution.
I need the admin events accessed only with path /admin/ to can apply further
security constraints to a certain path (in my case /admin/) if it will be
necessary.

I think the majority of webapps have an admin part and a public part.
How do you separate these parts?

Thanks,
Andras.