oh i see. thanks for the info. one more question: is it possible to do user registration with SGS?
if the user wanted to participate in a game, he/she needs to register first. but with the current SGS implementation, the login id and password are in the passwd.txt, which the application may not had access to. so what i have in mind is to use JSP, servlet and beans to read the passwd.txt file for existing password and to inform the user that that particular id has been taken else, it will update the passwd.txt of the new id and password. then the user can run the jar to login the game and play.
actually, i want to know how to do user registration with SGS.
The answer is that the FlatFileUserAuthenticator, as others have pointed out, is a minimal example intended as a guide and tool for developers.
The version of the SGS contaiend in the SDK is for <b>development purposes only</b>. You cannot, by the license, run a service for users outside of your development group with it.
A real service would likely write their own authenticator using the stack extension SDK. (Which is coming, but we've held up on releasing because we are doing an architectural review in light of the "big back end" which is the real, scalable server system that someone running a service would use. Its possible that as a result of this review some interfaces may chnage some and we didnt want you to run off and start writing code that would be incompatable with the actual production environment.)
This custom authenticator would talk to their own database, or however else they themselves manage users.