Le lundi 28 novembre 2011 à 22:58 +0100, André Warnier a écrit :
> It works, but it is your choice of language for the explanation which
> triggered my comment.
>
Well, you were right to point out the inaccuracy. I meant transparent to
the end user, who in my case is normally unlikely to run a
Le lundi 28 novembre 2011 à 14:15 -0800, Jay Scherrer a écrit :
> I would want to create or add a Database table connecting the user's to
> the company. This way a simple login could direct all customer requests
> to specific company websites.
Hi Jay,
The problem was to identify the client _befo
Le lundi 28 novembre 2011 à 23:26 +0100, André Warnier a écrit :
> you may want to try
>
>
>ServerName "as-pro.biz"
> ..
>
>
>ServerName "customer1.biz"
> ..
>
> That is much more flexible (and a lot less work in the long term) than
> adapting your
> software each time a customer w
On 28/11/11 03:26 PM, André Warnier wrote:
Vincent Veyron wrote:
Snip
That is why I was suggesting multiple sections.
Snip ...
This way, you can give each customer its own "special things" whenever they
want, without
interfering with your perl modules (or the other customer si
Vincent Veyron wrote:
..
tested it. See :
http://extranet.france-prevoyance.fr/clients/login
and :
http://as-pro.biz/clients/login
An additional comment :
The logic you have now (with the login module checking the hostname and choosing the logo
in function of that), is fine as long as the
I would want to create or add a Database table connecting the user's to
the company. This way a simple login could direct all customer requests
to specific company websites. And also linking to data tables and
special web directs. This will also increase service for your companies
by providing cus
Vincent Veyron wrote:
Le lundi 28 novembre 2011 à 20:37 +0100, André Warnier a écrit :
That way, the policy holder can type
'http://extranet.insurance_company.com/clients/login' and have access to
the data, transparently hitting my server at as-pro.biz.
Not really. I think you need to read up m
Le lundi 28 novembre 2011 à 20:37 +0100, André Warnier a écrit :
> >
> > That way, the policy holder can type
> > 'http://extranet.insurance_company.com/clients/login' and have access to
> > the data, transparently hitting my server at as-pro.biz.
>
> Not really. I think you need to read up more
Vincent Veyron wrote:
Hi Group,
I host a web service for my customers (ex : insurance_company.com) on a
virtual host (*); my customers in turn want their customers (the
policyholders) to have access to the data, while using their internet
name instead of mine.
This works fine with the ServerA
Hi Group,
I host a web service for my customers (ex : insurance_company.com) on a
virtual host (*); my customers in turn want their customers (the
policyholders) to have access to the data, while using their internet
name instead of mine.
This works fine with the ServerAlias directive inside the
10 matches
Mail list logo
