From: <won...@ya...> - 2002-06-26 09:52:28
|
Hi everybody, We are currently building a model of the Atlas server, that means, something relativly near what the Atlas server should be. Remember (written in a previous mail) what the Atlas server model should be able to: ATLAS SERVER STARTUP AND USER REGISTRATION: -1- JBoss deploys the Enterprise ARchive (myrpg-atlas.ear): -1.1- Catalina (Tomcat 4.0.3) deploys the Web Application Archive on http://:80/myrpg-atlas -2- On the first connection to the URL : http://:80/myrpg-atlas/index.jsp (JSP because we print on the homepage the date and time of server, eventually the number of currently connected users...): -2.1- If there is no administrator then the administrator registration page is displayed and the process begins. -2.2- If the Atlas server is not configured (SMTP host ) then the server configuration process starts. -2.3- If there is no RPG Master then the RPG Master registration page is displayed and the process begins. -2.4- Installation of the world (archive .world) in the Root directory of the Atlas server. -2.5- The RPG Master starts the Atlas server by using the Web Application (after loging in) à initialization, the world is online, start of the A.I. engine..., users have now access to the world. -3- A new user conects to the Web Application, registers and download an archive which contains HiCare (the client, the game window). He runs HiCare and then connects to the Atlas server by using his login and password. -4- He chooses or creates a character and plays to the game. Currently, step 2.1 is finalized and we have to build the server configuration process. Explanations of step 2.2: Once one administrator exists for the Atlas server, one has to configure the server with different properties: - the world name ot the atlas server (RPG MASTER) - the SMTP HOST (ADMINISTRATOR) - the URL (ADMINISTRATOR) - other properties... The first property would be administred by a RPG MASTER, others by the administrator. The first time the Atlas server is configured, only ADMINISTRATOR's properties have to be administred! The process can (must) reuse the code of the first administrator creation process. The configuration bean should be implemented, so the main work for this step should be in the JSP pages :) Wang and me will work on it... One can also begin to think about the others steps... Good Luck, Loic Lefevre ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |