• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Common application for different database users
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Common application for different database users


  • Subject: Re: Common application for different database users
  • From: "Cheong Hee (Datasonic)" <email@hidden>
  • Date: Wed, 15 Aug 2007 17:17:36 +0800

This is exactly what I tried to find out if there is any way to embed the
attribute into session, after redirection from apache:
e.g. www.mydomain.com/MyAppA  ..... redirect to something like
www.mydomain.com/cgi-bin/WebObjects/MyApp/(some cookies here so that session
could pick it up for database connection dictionary)
How do you go about it?  I did have the login panel in the Main component.

Cheers
Cheong Hee
----- Original Message ----- From: "James Cicenia" <email@hidden>
To: "Cheong Hee (Datasonic)" <email@hidden>
Cc: <email@hidden>
Sent: Tuesday, August 14, 2007 10:35 PM
Subject: Re: Common application for different database users



Can't you just have the user have an attribute that tells it what  company
it belongs too?
This presupposes that they have to log in. This is what we do with  our
hosted subscription
application and it seems to work very well.

Otherwise for a non-login system, I have used the wirehose framework  to
show different
catalogs etc. dependent on the subdomain.

-James

On Aug 13, 2007, at 10:16 PM, Cheong Hee (Datasonic) wrote:

I have the same application that is currently used by different  group of
users (or company).  I did it in JavaMonitor and gave them  different
name
for application instances and initialized them with few own  parameters
in
JavaMonitor.  So that when each group of them will access through:
www.mydomain.com/aaa        after webserver redirection for group  "aaa"
etc..
This made me maintains list of application instances.

The other option is to let user go to the common home page, and have a
selector to choose so that to differentiate the group of users.
 But this could be an issue, as it means other groups/companies are
exposed
to anyone who go to the common home page.

Is there any better way of design so that the same application  could be
used
to access their own database, while not to create list of different
application instances in JavaMonitor?

Cheers

Cheong Hee


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: 40jimijon.com

This email sent to email@hidden



_______________________________________________
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


References: 
 >Common application for different database users (From: "Cheong Hee (Datasonic)" <email@hidden>)
 >Re: Common application for different database users (From: James Cicenia <email@hidden>)

  • Prev by Date: Re: Common application for different database users
  • Next by Date: WO 5.3 Deployment on Windows
  • Previous by thread: Re: Common application for different database users
  • Next by thread: Re: Common application for different database users
  • Index(es):
    • Date
    • Thread