Full ASCII-only messages
In order to allow non-Java clients to communicate with the server and be a "channel selector", we need to get away from the transmission of Java objects. I have developed a new set of XML classes that can do this.
Need to implement this in the client and the server. The server needs to be aware that it might receive these ASCII-only messages and deal with it properly. It would probably be most efficient if the server were to figure this out when the client connects and the flag this client as ASCII-only.
I need to test the viability of the <signature>gobbeldygook</signature> XML tag -- does it really do the signature in a way that the server can interpret?
First step: allow selector clients to use this method. Second step: A web client for the displays (?)
#4 Updated by Elliott McCrory over 1 year ago
We will not have both Java object transmission and XML-as-ASCII transmission simultaneously. This would be unnecessary complication. Just implement the XML-as-ASCII and make the transition all at once.
Note that Java (Oracle) has announced that object streaming will soon be removed from the Java standard. So this has to be done!