Talk:Clan Wars Admin
From Wickle Wiki
A favor de RMI:
- llamadas desde el servidor para actualizar los datos de los clientes.
- No necesita correr bajo un servidor de aplicaciones (como tomcat)
Problemas de RMI:
- Problemas con proxys , callbacks son llamdas desde el servidor hasta el cliente para actualizar informacion ...
- se necesita la ejecucion de un programilla (rmic -d) para la generacion de stubs y skeletons.
- Aparentemente es un poco confuso de usar.
ejemplo:
http://www.ryerson.ca/~dgrimsha/courses/cps841/RMICallbacks.html
We need to evaluate a JMS container for this project, if finally we will be using JMS.
Proposals from the main page:
- To the messaging side i would like to use Jabber or JXTA protocol.
The architecture i am thinking on, is based on a Web Service on a central server and all clients using thin java clients to access remotely Web services.
Another option is JDNC and another one is Sockets , i think i need more discusions on that subject. More discussion about the architecture :
Someone proposed RMI Callbacks
(mirar http://www.ryerson.ca/~dgrimsha/courses/cps841/RMICallbacks.html )
We need to look at XML-RPC too, its simple but can only transfer text.
Another GREAT proposal is JXTA . Its a nice proposal and i think is a fine candidate to be the development platform.
Database at start on HSQLDB.
The two architectures on the head of discussion are JXTA and Jabber .. The first is winning by a head ;)
Well Another new friend of us JMS ... Its a nice candidate to develop the system on ... it has a lot of advanteges and very few disadvantages.
links on JMS : http://www-106.ibm.com/developerworks/java/library/j-jms/?dwzone=java
http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/basics.html
http://www.javaworld.com/javaworld/jw-02-2000/jw-02-jmsxml.html
Doubts about JMS or Jabber ...
Again i have doubts ... I am not sure if the best (or at least the choosen) platform would be JMS directly or use the jabber technology and approachs ...
