Is there a spec for how SES URLs work?
I've yet to convert my own stuff to SES, so some uniform understanding 
would help me, perhaps us.

My assumption was: 
"host.domain/directory/directory/file.ext/name/value/name/value..."
Is it simply like that?

If so, a CF* parse might go something like:
Ignore anything before ://
Anything before listFirst(url,"/") is host.domain
Anything after listFirst(url,"/") and before 
listGetAt(url,listFind(url,".","/"),"/")) is a directory path
Anything after listGetAt(url,listFind(url,".","/"),"/")) - or the "?" 
char - is a sequence of name/value pairs
Translate name/value pairs into name=value pairs, respect traditional 
name=value pairs as well
Build a new list of name=value pairs with "&" as the delimiter
Prepend the whole list with "?" and bada bing: there's your traditional 
query string

That would translate 
http://www.example.com/index.cfm/go/home/ into 
http://example.com/index.cfm?go=home
in a sub dir:
http://www.example.com/foo/index.cfm/go/home/ into 
http://example.com/foo/index.cfm?go=home
the traditional
http://www.example.com/foo/index.cfm?go=home into 
http://example.com/foo/index.cfm?go=home
the multi var
http://www.example.com/foo/index.cfm/go/home/bug/soup/ into 
http://example.com/foo/index.cfm?go=home&bug=soup
and finally, the mutt
http://www.example.com/foo/index.cfm/go/home/?referrer=google into 
http://example.com/foo/index.cfm?go=home&referrer=google

(but it would not translate 
http://example.com/index.cfm?go=home?referer=google - if someone 
actually entered that.)

But all that - only if I understand the SES spec correctly, if there is one.

* Not that one would actually use CF to do this work, it's just some 
handy syntax to use here for my stream of consciousness pseudocode .

Alan K. Holden


--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to