I have been studying the code of JavaMUD and i have a doubt right now.
When u want to add a new area or a new class or some other change, u have to stop the server, and then start it again so it can load the new .class archives? Or u can simply add the .class to a specified dir, like lpmuds do.
So the overall question is, a Java based MUD needs to load all the .class in the memory at startup, so little changes needs a restart of the server?
Thank you too much
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Basic LPmuds are based on using a .c-like environment, thus a basic 'load once, use many' setup.
Since the files are in fact classes, Java isn't capable of a drop-in data file and recompile on the fly setup, so yes, you will have to stop the server, rebuild, then restart.
Javamud is close in relation to LPmuds by how the rooms and objects are structured (ie. set_short(), set_long(), etc). Yes, they are a bit hardcoded but I think if the SQL interface could be used w/ the code, it might be possible to have a sort of daemon to call from the database then build objects and rooms from tables, etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This MUD has admin commands that allow it to invoke the "javac" compiler and the driver will automatically reload the class file when next time it is requested to be cloned.
Also you can force to reload an already loaded object.
I have been studying the code of JavaMUD and i have a doubt right now.
When u want to add a new area or a new class or some other change, u have to stop the server, and then start it again so it can load the new .class archives? Or u can simply add the .class to a specified dir, like lpmuds do.
So the overall question is, a Java based MUD needs to load all the .class in the memory at startup, so little changes needs a restart of the server?
Thank you too much
Basic LPmuds are based on using a .c-like environment, thus a basic 'load once, use many' setup.
Since the files are in fact classes, Java isn't capable of a drop-in data file and recompile on the fly setup, so yes, you will have to stop the server, rebuild, then restart.
Javamud is close in relation to LPmuds by how the rooms and objects are structured (ie. set_short(), set_long(), etc). Yes, they are a bit hardcoded but I think if the SQL interface could be used w/ the code, it might be possible to have a sort of daemon to call from the database then build objects and rooms from tables, etc.
No, this is not entirely true.
This MUD has admin commands that allow it to invoke the "javac" compiler and the driver will automatically reload the class file when next time it is requested to be cloned.
Also you can force to reload an already loaded object.
See:
javamud.driver.refresh_object()
javamud.driver.reload_object()
javamud.object.wiz.acl_mod.java
regards
Istvan David