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
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
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
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to clearsk...@googlegroups.com
I'm fine with that. I will move the ruby implementation into its own
repository.