Separate protocol and clients in different repositories

21 views
Skip to first unread message

Pedro Larroy

unread,
Mar 16, 2014, 9:28:28 AM3/16/14
to clearsk...@googlegroups.com
Hi

I think we should separate the protocol specification in a different repository than the implementations. So we allow having clients going at different speeds and it's not confusing to have a client with an old protocol implemented together with the protocol description.

@jewel: I this it's appropiate if you manage this repository under your account. 

Pedro.

Steven Jewel

unread,
Mar 17, 2014, 12:51:20 PM3/17/14
to clearsk...@googlegroups.com
I'm fine with that. I will move the ruby implementation into its own
repository.

Steven
Reply all
Reply to author
Forward
0 new messages