Issue Details (XML | Word | Printable)

Key: DOL-135
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Dierk Koenig
Reporter: Andres Almiray
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Dolphin

Let Codec handle other inputs such as Reader and InputStream

Created: 21/Jan/15 12:30 PM   Updated: 23/Mar/16 09:46 AM
Component/s: Communication-Level
Affects Version/s: 0.11
Fix Version/s: None
Security Level: public

Time Tracking:
Not Specified


 Description  « Hide
The current org.opendolphin.core.comm.Codec interface defines a single decode() method that takes a String as input. It would be better for integration with Java based codebases if the Codec could handle java.io.Reader and java.io.InputStream too.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dierk Koenig added a comment - 22/Jan/15 04:28 PM
I see the principle value but inside OpenDolphin, the codec is never used other than for a String nor is it apparent that it will ever do so.

I'd say we can defer the effort (and the effort of testing it) until we need such a feature.


Andres Almiray added a comment - 23/Mar/16 09:46 AM
I can see OpenDolphin being used in environments where HTTP and JSON are not the transfer protocol nor the encoding mechanism. Other transport options may be Netty, Aeron. Additional encoding mechanism may be Kryo, Messagepack, Simple Binary Encoder. These options provide a better throughput and/or data transfer rates. Some of them do not work with Javascript but that's beside the point. This issue was created to open the possibility to write such codecs targeting Java only applications.

PS: it's possible to use Messagepack as encoding mechanism for JS too.