Re: changing application behaviour according to domain name
Re: changing application behaviour according to domain name
- Subject: Re: changing application behaviour according to domain name
- From: Guido Neitzer <email@hidden>
- Date: Thu, 30 Jun 2005 15:57:03 +0200
On 30.06.2005, at 15:02 Uhr, <email@hidden>
<email@hidden> wrote:
There are many ways depending on what exactly you want to achieve.
Yes, okay. I wasn't clear with that.
Currently we have single machine for this application(s). On the long
term we will have a bunch of "portal" applications that share a
common design (with small differences in colors or used buttons - no
problem with different stylesheets).
The portals will have different content, different colors, a few
differences on available searches, slightly different navigation -
nothing that can't be handeld with different config files or database
entries and some decisions what components should be used.
They will be accessed through different domains and will (as long as
possible) be completely stateless. Currently we have one machine,
later we will have perhaps (I hope so) more.
I have no problem with deploying the same application xx times on the
same server if this is possible without much trouble (never tried that).
For short: it would be enough for me to have one application deployed
as "app1", "app2", "app3", ... with either different config files and/
or a commandline argument telling the app what to display.
I like the idea of changing some things once, deploy the app, rename
(duplicate the bundle or whatever) and start the instances with
different parameters. I can store every information I need in the db
or in external config files, all no problem, I have full control
currently as I'm just switching the first of the portals to a
stateless app rewriting it more or less completely.
Will you have one server to host all domains or merely deploy the
same code to different servers each responsible for one domain.
With the latter setup I would note all that differentiates the
environments in property files differing on each machine.
This is not what I prefer because it's just unnecessary expensive. We
don't have that much traffic and the Mac mini would be the only
affordable plattform to go this way ... :-)
1. A single WOTask managing several sets of instances of the same
application code base. YOu declare several applications in
JavaMonitor and have them point to the same installed application
bundle. Customization of the application is made at startup based
on a command line argument. This may well be the application name.
Using Apache virtual hosts you could rewrite / to point to
applications URLs differing for each host.
If this works, it would be great. I think I will test exactly this.
Thank you for your information!
Guido
_______________________________________________
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