Is it possible to change the "/messagebroker/amf/", from the view of the webserver?

Question

I have BlazeDS integrated into a J2EE application.  All method innvocations from the Flash client flow through an Apache webserver, until it reaches its destination of the J2EE application.  The Flash client exercises several distinct methods through this BlazeDS service.
My question is, from an Apache webserver perspective, is there a way for Apache to distinguish one method from another?  Right now, Apache views everything as a POST to the URI of "../messagebroker/amf".  The options seem to be:
1)  Dig into the POST to find the method signature.  This seems scary given the POST has binary content.
2)  Try to change the URI of "../messagebroker/amf" for each method.  I have no idea how to go about this.
3)  Maybe include a method signature in the http header?  Again, not sure how to do such a thing in Flash/Flex.
If anyone has addressed this requirement in the past, I'd be very greatful for some advice.

Answer 1

Hi. I haven't heard of anyone trying to do this in the past. I'm just curious, why does the Apache server need to know what method is being called?
I would think something like 2) you could do mostly on the Apache side. Just brainstorming here but in your client application(s) you could manually create a ChannelSet with a channel that had the method name in the uri, so for example "../messagebroker/amf/method1" and "../messagebroker/amf/method2". The apache server could then do whatever it needed to do for the individual methods and redirect all requests to "../messagebroker/amf".
Here is a link to the BlazeDS documentation that deals with channels and endpoints. That has some information on manually creating a ChannelSet and channels on the client in case you decide to go that route.    
http://livedocs.adobe.com/blazeds/1/blazeds_devguide/help.html?content=lcconfig_2.html
Hope that helps.
-Alex