Documentation Required about fleck HOT 4 CLOSED

What states would you consider the server to have?
On Jul 1, 2012 6:36 PM, "qJake" <
[email protected]>
wrote:

There should be a Status property on the WebSocketServer class that
returns a WebSocketServerStatus enum of the server's current status.

Additionally, the WebSocketServer should have a Close() method
allowing the server connections to be closed.

---

Reply to this email directly or view it on GitHub:
#44

from fleck.

Would you be interested in writing some?
On Jul 1, 2012 7:22 PM, "qJake" <
[email protected]>
wrote:

There needs to be XML documentation for this project so that people have a
better understanding of how to use the library.

---

Reply to this email directly or view it on GitHub:
#44

from fleck.

Sorry about the ninja-edit, I failed to understand the architecture between the server and the conneciton object.

Your public void Start(Action<IWebSocketConnection> config) method... the "config" parameter should probably be renamed to something like "OnClientConnected" - at first, I wasn't saving the connection objects because I didn't realize how valuable they were. Perhaps a better example demonstrating saving and broadcasting to multiple clients is in order.

And no, documentation writing is not really my forté, sorry, plus I'm too busy writing a WebSocket server from your library for a project I'm working on. :)

from fleck.

The console application sample is an example of broadcasting to multiple
clients.

A rename could be useful for clarity.

As for documentation, I will take a look at adding a few bits the next time
I dive into the Fleck source.
On Jul 1, 2012 10:21 PM, "qJake" <
[email protected]>
wrote:

Sorry about the ninja-edit, I failed to understand the architecture
between the server and the conneciton object.

Your public void Start(Action<IWebSocketConnection> config) method...
the "config" parameter should probably be renamed to something like
"OnClientConnected" - at first, I wasn't saving the connection objects
because I didn't realize how valuable they were. Perhaps a better example
demonstrating saving and broadcasting to multiple clients is in order.

And no, documentation writing is not really my forté, sorry, plus I'm too
busy writing a WebSocket server from your library for a project I'm working
on. :)

---

Reply to this email directly or view it on GitHub:
#44 (comment)

from fleck.