Good idea that will help with internal access but the "users" will be primarily people form outside the company so that won't work for them.
on 11/3/03 12:59, Roland A. Dumas at [EMAIL PROTECTED] wrote: > is this so that people hitting the site FROM each of the companies > will see it as their own? > (if so, in your index.taf, you can assign a global variable based on IP > or client domain and use that to change the presentation) > On Nov 3, 2003, at 9:42 AM, Dan Stein wrote: > >> I prefer to have the domains point as you do but in the case the deal >> is the >> client owns a much wanted domain that multiple companies want as their >> own. >> Rather than sell it to one he wants to serve all of them in the way >> described. >> >> on 11/3/03 11:47, Robert Shubert at [EMAIL PROTECTED] wrote: >> >>> I prefer to have 6 specific domains that all point to the same >>> physical >>> website, then you can logically separate the content by domain, this >>> works well. >>> >>> Otherwise, I would simply take >>> >>> www.site.com/xyz/default_file.taf >>> >>> And have it @ASSIGN user$site = xyz >>> >>> Then META-REFESH www.site.com >>> >>> Then have all your TAFs in www.site.com/ be able to look at the >>> user$site to determine what you present. >>> >>> You will likely have a problem with bookmaking, and will need to deal >>> gracefully with a user at www.site.com without a USERREFERENCE and/or >>> user$site set. >>> >>> Robert >>> >>> -----Original Message----- >>> From: Dan Stein [mailto:[EMAIL PROTECTED] >>> Sent: Monday, November 03, 2003 11:29 AM >>> To: [EMAIL PROTECTED] >>> Subject: Witango-Talk: Looking for thoughts >>> >>> I am drawing up specs for where there will be multiple hosting >>> multiple >>> domains from a single backend. >>> >>> In each case we will have multiple companies in each domain but will; >>> want >>> to load specific sites to those companies when users come into the >>> domain. >>> >>> So for instance there may be 6 companies who will all have the domain >>> appearing in the address part of the browser being >>> >>> www.thissite.com >>> >>> But because as user came in through www.thissite.com/xx they will get >>> a >>> specific companies site. >>> >>> I want the links to always be hidden so even the www.thissite.com/xxx >>> does >>> not appear in an address bar. >>> >>> The site will in 90% of the cases be flash based and will not have >>> eCommerce >>> functionality. >>> >>> I'm looking for ideas on how to best design this and what the pitfalls >>> and >>> pros and cons might be, >>> >>> Dan >> >> -- >> Dan Stein >> Digital Software Solutions >> 799 Evergreen Circle >> Telford PA 18969 >> Land: 215-799-0192 >> Mobile: 610-256-2843 >> Fax 413-410-9682 >> FMP, WiTango, EDI,SQL 2000 >> [EMAIL PROTECTED] >> www.dss-db.com >> >> >> "When you are born, you cry and those who love you rejoice. And >> if you >> live your life as you should, when you die, you rejoice and those who >> love you cry." >> >> _______________________________________________________________________ >> _ >> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf >> > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > -- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 Land: 215-799-0192 Mobile: 610-256-2843 Fax 413-410-9682 FMP, WiTango, EDI,SQL 2000 [EMAIL PROTECTED] www.dss-db.com "When you are born, you cry and those who love you rejoice. And if you live your life as you should, when you die, you rejoice and those who love you cry." ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
