Thanks for the quick reply Kurt. No, I did not know about UrlRoutes, so I will definitely look into those.
One other example I forgot to add to my original message was the addition of one more / delimited element in the URL processes the event name properly.
Ex. 3:
http://testwebsite.local/index.cfm/testSES/1/2/?foo=bar&blow=chunksThe resulting event argument struct then looks like:
1 = 2
foo = bar
blow = chunks
event = testSes
This pattern is repeated so as long as there are an odd number of '/' delimited arguments. The reason I assumed the example 2 pattern would work (from my original message) was I figured M2 parsed the first element in the cgi.path_info to get the actual event. This appears to be the case when you add the "event" parameter back into the URL string since in that case it does not matter how many name/value "pairs" can be matched in the cg.path_info (hence the reason the struct key 1 had an empty string value in example 1), yet it still parses the correct event name (testSES). Does my additional example make sense?
I guess my main issue is I would expect M2 to behave the same in processing SES URLs regardless of whether or not I indicate to ignore the event parameter. This is definitely not the case in my various tests.
Basically what I am using this for is a RESTful API interface to my application. I really do not care about the event arguments that M2 parses for me, rather I care that it gets to the correct event for processing purposes.
-JSLucido