Printable View
Hey, im trying to track if a user is logged in or not, ive made a login screen, which connects to a database and checks if the user exists, when if they exist, another window pops up, how can I check if the username exists without having to do another database query? Im not using servlets and when searching for examples those are the only ones im getting. Its not on a website, its a application.
Anyone know how I would be able to do this?
andQuote:
if a user is logged in or not
It runs only on a user's PC without connection to the internet?Quote:
not on a website , its a application
What does a 'session' mean in the context of someone using a program on their own computer? Are there different people using this program on the same computer at different times?Quote:
how I would be able to do this
At the moment I have two seperate Java files, one which acts as my client ( where the gui is) and another which is on another machine which acts as the server.
the client java file, opens up a gui, gets the user input (username and password) then passes it to the server through sockets. The server part of the java file then creates a prepared sql query from the information username and password that was passed to it, and returns whether or not the user exists.
These two java files are on different machines, different networks, that part works fine.
If the client side recieves a "ok user exists" reponse, a second java gui opens up. What I was hoping to do was somehow protect the second gui from being accessed if a session isnt currently running, without having to do another database query to check if the username and password are still valid.
Whenever i search for session examples I get heaps of ones for servlets, and httpsessions, which I dont think is what im looking for, if there are any other methods of doing this I would really appricate any suggestions :)
Session info can be keep by using cookies. The server adds a Set cookie to the HTTP response header field with a cookie that the server can use to maintain the status of a client. The next request from the client must return that cookie in its HTTP request header.
The server would need a cookie management scheme.
They're not talking http though, from what I can gather.
OK, so you have a login screen...the user logs in...it's successful.
How do you define "protect the second gui"? How do you think someone will get at the second gui without logging in?
They need their own protocol taking the cookie idea from HTTP to preserve session state.
Possibly, but since the whole gui seems to be on the client anyway it's not a very good match.
Without actually knowing what they're up to I would be loathe to suggest mimicking a session setup.
I guess we need the OP to clarify what he wants.