Branding/Skinning approaches
Branding/Skinning approaches
- Subject: Branding/Skinning approaches
- From: Kieran Kelleher <email@hidden>
- Date: Wed, 20 Sep 2006 09:50:34 -0400
Hi all,
Just trying to decide how to best approach "skinning" on an app for
wholesale resellers of our services. Our primary caveat that needs to
be taken into account is that we use SSL https pages primarily
throughout the app.
I am thinking that the fastest approach is to create a direct action
with a reseller param for the main entry point of the app and push
the associated skin object into the Session. Basically I would be
abandoning any hope of using sessionless pages then of which I only
have a few for the prevention of sessions for non-logged in users.
Then I can just use "cloaking" (frame the whole page) on the
reseller's domain name to hide my URL.
The probably better longer term approach is to get an SSL certificate
that is tied to my IP address instead of my domain name so that all
the reseller domain names point to my IP and I just use the incoming
request host name to determine which skin (basically CSS and page
brand banner) to use.
Any inputs on what has worked best or gotchas?
Regards, Kieran
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden