re: DirectAction & User login Questions.
re: DirectAction & User login Questions.
- Subject: re: DirectAction & User login Questions.
- From: Andrew Lindesay <email@hidden>
- Date: Thu, 14 Feb 2008 10:42:43 +1300
Hello Daniel;
I want the app to create no session until a user successfully logs
in. Based upon what I have found this is the right way to do it:
public Application() {
NSLog.out.appendln("Welcome to " + name() + " !");
/* ** put your initialization code in here ** */
setDefaultRequestHandler
(requestHandlerForKey( directActionRequestHandlerKey() ));
}
You need to be careful that nothing you are doing in Main is causing a
session to be created. Try putting a breakpoint in the session
constructor to understand why this is happening. The default DA
should look for the authentication details and respond with the right
component if the authentication was successful; otherwise return Main
without doing anything that could create a session.
On the WebObjects Wiki/confluence, it is stated that people typing
in URLs with your components could cause problems. So how do I keep
people from doing so?
See my framework "LEWOStuff"...
LEWOApplication.createRequest(..)
This has a javadoc note about it.
If I have a user/passwords login app, how do I keep people from
using a common username and password simultaneously on different
computers? There will be multiple application instances, on several
servers.
Can you define what you want here -- you want people to be able to
login from only one client host using a web browser?
cheers.
___
Andrew Lindesay
technology : www.lindesay.co.nz
business : www.silvereye.co.nz
_______________________________________________
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