Re: Barracuda: case-insensitive event names?
Ron Alsobrook <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
I would be interested in this too since every now and then I get some errors because of all lowercase URLs that (I guess) are being typed into a browser by hand. Ron -----Original Message----- From: Jacob Kjome Sent: Thursday 12 December 2002 1:31 pm Subject: Barracuda: case-insensitive event names? > Hi everyone, > > I'm just wondering if there is a way to make the event names in a url > treated as case-insensitive? Is that possible currently? I hadn't > really thought about it until now, but if you have an event named > something like "MyEvent" and you called it via > http://localhost:8080/MyEvent.event, as long as you specified an event > interest for that event, you could handle it. However, what if > someone writes it as http://localhost:8080/myevent.event. Currently, > Barracuda doesn't seem to recognize the event as a "MyEvent" even > though it is spelled exactly the same way and it is pretty obvious > that "MyEvent" is the event meant to get triggered. > > Is there any way to make events provided via a URL case-insensitive? > Unlike case-sensitivity on the file system via running a website on a > Unix machine (eg... Index.html -vs- index.html), we should be able to do > any mapping we want in the application/event gateway. > > If we did implement this, would there be any pitfalls to look out for? > I can't really see any unless it were possible for Java classes to be > named the same thing in the same package with the only difference > being case, such as "MyEvent.java" and Myevent.java". Is that > possible on Unix? It isn't on Windows, that's for sure. > > The other situation that could bite back is the case where the same > named event existed multiple times, but in different packages. If all > those events were registered to be handled by various handlers, which > handler would actually get triggered? However, this is a problem even > outside the issue of case-sensitivity, so it is kind of a separate > issue. But now that I bring it up, how would this situation be resolved > (other than just being diligent about naming events uniquely)? > > Comments? > > Jake _______________________________________________ Barracuda mailing list [email protected] http://www.enhydra.org/mailman/listinfo.cgi/barracuda FAQ - http://www.jguru.com/faq/Barracuda