Hi Dan, Technically it could work...up to a point.
Yes, Witango can work with dynamic Datasources, and using the method Robert Shubert suggested would work for dynamically assigning which Datasource to use, based on a sub- folder. You could use something like <@APPFILEPATH> to extract which sub-folder they entered on, then assign the appropriate Variables which would deliver dynamic content for the Users - all served from a single set of files. After dynamically assigning which datasource to use, you could re-direct them to the root address. But what if they don't enter from a sub-folder address? All the customers would have the same root address, so instinctively people like to start at the root when manually typing the address - so what identity would you serve up as the default? This would affect public and private users equally. And what about Search engines? What information would you serve up to them when they hit the root address first? Remember, a Searchbot won't utilize session-cookies (with or without <@USERREFERENCE>). I think to some degree you could write enough code to protect yourself against missing certain required variables, but when about bookmarks to "public" content? This could be a nightmare. I think your customer is not thinking this through all the way. Technically it could work, but you're looking at some headaches down the road. This will be true no matter what platform you develop on. Just my 3 cents (Canadian exchange catching up to USD, eh :-) Good luck. Cheers...... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xmlx.ca 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- -----Original Message----- From: Dan Stein <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Date: Mon, 03 Nov 2003 13:25:59 -0500 Subject: Re: Witango-Talk: Looking for thoughts > Ben, > > I don't see the problem. The DNS points to the domain we want everyone > to > see. Then all we are doing is loading a different web site depending > on how > they come in but hiding all the links through frames or forms so the > browser > URL address always remains the same. > > on 11/3/03 13:13, Ben Johansen at [EMAIL PROTECTED] wrote: > > > I see a big problem with this, because DNS take a domain name and > link > > it to one IP address; hence there is no way to determine which > context > > the end user is looking at domain. > > > > The sub-domain option like Rick suggested is the only way I can see > the > > domain being visible for all who want to be associated with it. > > Abc.domain.com, def.domain.com > > > > Or you will have to have a main page with links to all who are > > associated with that domain > > > > Ben Johansen - http://www.pcforge.com > > Authorized Witango & MDaemon Reseller > > Available for Witango Developement > > > > > > -----Original Message----- > > From: Dan Stein [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 03, 2003 9:43 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Witango-Talk: Looking for thoughts > > > > 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
