K
Karsten Wutzke
Hello!
I'm currently developing a chat client. I want to design the software
for protocol independence. It ought to be a very simple design, I
don't want to create a general purpose protocol (framework). The
protocol consists mainly of textual data to be put on and read from
the socket In/OutputStream's. For the client to use the software, it
should not be visible, whether the user's chat is running via server X
with protocol X or it runs on server Y using protocol Y. In any case,
the server (or IP range) is expected to know only one protocol.
Maybe there's a simple pattern for it? Maybe something more trivial
(simple subclassing)?
Can you share your experience how I might proceed?
Thanks
Karsten
I'm currently developing a chat client. I want to design the software
for protocol independence. It ought to be a very simple design, I
don't want to create a general purpose protocol (framework). The
protocol consists mainly of textual data to be put on and read from
the socket In/OutputStream's. For the client to use the software, it
should not be visible, whether the user's chat is running via server X
with protocol X or it runs on server Y using protocol Y. In any case,
the server (or IP range) is expected to know only one protocol.
Maybe there's a simple pattern for it? Maybe something more trivial
(simple subclassing)?
Can you share your experience how I might proceed?
Thanks
Karsten