Dave Robin

By default, all the behavior of the reference implementation complies with the standard. Since the use of "plain" WebSockets is not allowed by the standard, you have to specifically enable it with a configuration property: sc.allowPlain = true A note about this has been added to the README that will be pushed out with the 3.2 changes.

Oh yes, it runs on a Raspberry Pi! Since I had one sitting on my desk, it was always an informal design target. I say "informal" because it is not specifically a "supported" platform along with Linux, Windows, and Mac, but it was certainly a personal design goal to make sure that it ran and performed reasonably well on a $30 device :-) I ran it under Version 9 "stretch" on a Model B Plus 1.3. As a hub, it accepted 100 simultaneous connections, and I called that a success. I didn't do much more testing...

Oh yes, it runs on a Raspberry Pi! Since I had one sitting on my desk, it was always an informal design target. I say "informal" because it is not specifically a "supported" platform along with Linux, Windows, and Mac, but it was certainly a personal design goal to make sure that it ran and performed reasonably well on a $30 device :-) I ran it under Version 9 "stretch" on a Model B Plus 1.3. As a hub, it accepted 100 simultaneous connections, and I called that a success. I didn't do much more testing...

Often, the primary goal of a “reference implementation” is to be correct in its behavior, and equally, to be easily understandable and fixable by a community if it is found to be not correct. It is a “known good” against which other implementations are to be measured. In many cases then, it is only a secondary goal that it be a “starting point” for vendors‘ implementations. This balance of priorities can be seen in the extensive and verbose logging that is done by this implementation. That large...

Often, the primary goal of a “reference implementation” is to be correct in its behavior, and equally, to be easily understandable and fixable by a community if it is found to be not correct. It is a “known good” against which other implementations are to be measured. In many cases then, it is only a secondary goal that it be a “starting point” for vendors‘ implementations. This balance of priorities can be seen in the extensive and verbose logging that is done by this implementation. That large...

Often, the primary goal of a “reference implementation” is to be correct in its behavior, and equally, to be easily understandable and fixable by a community if it is found to be not correct. It is a “known good” against which other implementations are to be measured. In many cases then, it is only a secondary goal that it be a “starting point” for vendors‘ implementations. This balance of priorities can be seen in the extensive and verbose logging that is done by this implementation. That large...

.DS_Store removed

Initial commit