Project

General

Profile

Feature #13155

Full ASCII-only messages

Added by Elliott McCrory about 4 years ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Elliott McCrory
Category:
Java Code
Start date:
07/07/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Duration:

Description

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 (?)

Subtasks

Feature #13160: Test viability of the "signature" XML tag in all-ASCII messagesClosedElliott McCrory

History

#4 Updated by Elliott McCrory almost 2 years 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!

#5 Updated by Elliott McCrory 5 months ago

  • Status changed from New to Resolved

Also available in: Atom PDF