Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is the SocketNamespace#emit api private? #538

Closed
coreh opened this issue Sep 25, 2011 · 2 comments
Closed

Why is the SocketNamespace#emit api private? #538

coreh opened this issue Sep 25, 2011 · 2 comments

Comments

@coreh
Copy link
Contributor

coreh commented Sep 25, 2011

The @api for SocketNamespace#emit is labeled as private: https://github.com/LearnBoost/socket.io/blob/master/lib/namespace.js#L183

/**
 * Emits to everyone (override)
 *
 * @api private
 */

Is this method really meant to be private, or was it labeled incorectly? Is there a way to achieve this functionality without resorting to io.sockets.emit()?

Thanks.

@rauchg
Copy link
Contributor

rauchg commented Sep 25, 2011

Sorry, that's a typo.

@3rd-Eden
Copy link
Contributor

probably labeled incorrectly.

On Sun, Sep 25, 2011 at 9:37 PM, Marco Aurlio <
[email protected]>wrote:

The @api for SocketNamespace#emit is labeled as private:
https://github.com/LearnBoost/socket.io/blob/master/lib/namespace.js#L183

/**
* Emits to everyone (override)
*
* @api private
*/

Is this method really meant to be private, or was it labeled incorectly? Is
there a way to achieve this functionality without resorting to
io.sockets.emit()?

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

~ Arnout Kazemier
@3rdeden, V1 - IRC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants