Design patterns for communication protocols?

Hi,

I’m about to implement some custom communication protocols for a
distributed
system. Anyone got pointers to good designs, design patterns etc that I
should
not miss before embarking on this? Everything OO is relevant but best
is of
course if it is implemented in Ruby or has a Ruby flavor.

Thanks in advance,

Karsten

···


http://fastmail.fm - One of many happy users:
http://www.fastmail.fm/docs/quotes.html

Hello coma,

Friday, September 27, 2002, 2:27:38 PM, you wrote:

I’m about to implement some custom communication protocols for a
distributed
system. Anyone got pointers to good designs, design patterns etc that I

erlang programming language

···


Best regards,
Bulat mailto:bulatz@integ.ru

Have you considered BEEP? It’s an IETF standard for designing application
protocols. There is good software in several languages. There’s even an
O’Reilly book covering it. There are rumours of a ruby implementation but
I’ve not found it yet.

There are parts of the O’Reilly book that would be worth a read regardless,
especially the discussions around designing and implementing application
protocols.

Cheers,
Bob

···

On 9/27/02 6:27 AM, “coma_killen@fastmail.fm” coma_killen@fastmail.fm wrote:

I’m about to implement some custom communication protocols for a distributed
system. Anyone got pointers to good designs, design patterns etc that I should
not miss before embarking on this? Everything OO is relevant but best is of
course if it is implemented in Ruby or has a Ruby flavor.

Have you considered BEEP? It’s an IETF standard for designing application
protocols. There is good software in several languages. There’s even an
O’Reilly book covering it. There are rumours of a ruby implementation but
I’ve not found it yet.

There are parts of the O’Reilly book that would be worth a read regardless,
especially the discussions around designing and implementing application
protocols.

Cheers,
Bob

···

On 9/27/02 6:27 AM, “coma_killen@fastmail.fm” coma_killen@fastmail.fm wrote:

I’m about to implement some custom communication protocols for a distributed
system. Anyone got pointers to good designs, design patterns etc that I should
not miss before embarking on this? Everything OO is relevant but best is of
course if it is implemented in Ruby or has a Ruby flavor.

Have you considered BEEP? It’s an IETF standard for designing application
protocols. There is good software in several languages. There’s even an
O’Reilly book covering it. There are rumours of a ruby implementation but
I’ve not found it yet.

I’ve had this listed on rubyxml.com for a while:
http://www.rubyxml.com/raa/details#Ruby%20BEEP%20Core

and

Ruby BEEP Core download | SourceForge.net

James

···

There are parts of the O’Reilly book that would be worth a read
regardless,
especially the discussions around designing and implementing application
protocols.

Cheers,
Bob

Sorry James, I could have been a lot clearer in my wording. I knew about
these pages (they are linked to from the beepcore.org pages too) but there
is nothing available on source forge. I don’t know what the status of the
project is. It started May/July 2001, but nothing yet.

Cheers,
Bob

···

On 9/30/02 2:04 AM, “JamesBritt” james@jamesbritt.com wrote:

O’Reilly book covering it. There are rumours of a ruby implementation but
I’ve not found it yet.

I’ve had this listed on rubyxml.com for a while:
http://www.rubyxml.com/raa/details#Ruby%20BEEP%20Core

and

Ruby BEEP Core download | SourceForge.net

Sorry James, I could have been a lot clearer in my wording. I knew about
these pages (they are linked to from the beepcore.org pages too) but there
is nothing available on source forge. I don’t know what the status of the
project is. It started May/July 2001, but nothing yet.

Thanks for pointing this out. I checked the link to see if it was still
valid, but didn’t look closely at the page. The project offers four mailing
lists but no downloadable files. I’ve update my listing to indicate the
project may be in limbo. If anybody knows different, please let me know.

Thanks,

James

···

Cheers,
Bob