My Fellow Monks,
I am a sysadmin / engineer for an ISP and we have a website appropriately named "Vertex" that myself and a few other Monks, Russ
, Super Monkey
, and Jerry
all have spent some time on. Recently I started trying to setup a aptly named "My Vertex" configuration tool to scope the look and feel to a more per-user based, um basis ;). Cookies seemed like the right way so I read up on them, implemented and everything was grand, cept one thing. The domain of these cookies has to be static. My ISP covers 15 markets and hence has 15 sub-vertexs subdomains as such:
phoenix-vertex.*******.net, fresno-vertex.*****.net, etc...
The current way I have thought of was just having a centralized place for configuring cookies, and each time a user logs into one of the other boxes, the cookies for that box are fetched, if they exist, the user enters with a configured looks. ELSE, they are redirected to the central location, with the return url passed via CGI, then central location checks to see if they have a config, then passes it back via CGI so that they can be set locally on the first accessed box. If they do not have them set, they are sent to a configuration page, then so on and so forth.
My question for the monistary is if anyone else has tried to achieve the same goal I have in a different manor, or if there is something I am over looking that simplify this whole ordeal. Any help will be much appreciated.
"Never underestimate the predicability of stupidity"
- Bullet Tooth Tony, Snatch (2001)