Comments (9)
What about just rewriting the transports to not extend Client but implement a "Transport" interface and let Client use a Transport using dependency injection?
From what I've seen giving the source a quick glimpse extend is only used for the transports. Avoiding extend alltogether makes it possible to just use native "classes".
from socket.io.
It's not only about extend, it's also about mixing in other prototypes elegantly (options, eventemitter), and user-defined ones in the future (ie: plugins)
from socket.io.
So having a simple augment() function to augment a prototype with another object should also be enough?
function augment(to /*, from */) {
var i, k, from;
for(i = 1; i < arguments.length; i++) {
from = arguments[i];
for(k in from) {
to[k] = from[k];
}
}
}
So you can do
augment(Listener.prototype, process.EventEmitter.prototype, Options);
from socket.io.
It definitely could, but IMHO then the class looks confusing. Just take a look at node's http.js to see what I mean, and see if you can quickly tell classes apart, identify the contructor quickly, see what they inherit / mixin etc. Anyway, I'm open to this possibility too, I just don't see any disadvantage from using class.js.
from socket.io.
JSlint specifies that constructor functions should start with a capital and normal function should never start with a capital.
See http://www.jslint.com/ and especially the "Require Initial Caps for constructors" option.
It seems like http.js in node also obey's this standard.
Also I found http://www.crockford.com/javascript/inheritance.html quite enlightening about this subject. Especially the last paragraph on the page.
from socket.io.
After examining http.js in node it seems that node already has this augment() function I described it's called sys.inherits
so it turns out to sys.inherits(Listener, process.EventEmitter);
Edit: after checking out sys.inherits. it doesnt work like augment but it is a try to mimic classical inheritance working as a extend method.
from socket.io.
Yep, I've read that page many times. Unfortunately the last paragraph is anecdotic, and doesn't reflect in reality:
ClientRequest.prototype.end = function () {
if (arguments.length > 0) {
throw new Error( "ClientRequest.prototype.end does not take any arguments. "
+ "Add a response listener manually to the request object."
);
}
OutgoingMessage.prototype.end.call(this);
};
That's uber
being used, but without the handy shortcut.
from socket.io.
(The same goes for most of the constructors in http.js
)
from socket.io.
Then still.. it seems like almost everything that js-oo provides is already by default in Node.js in the form of that sys.inherits() except for the mixin part (wich the augment function I posted provides).
I guess using those two is more minimal and lightweight than any other external library ;)
from socket.io.
Related Issues (20)
- emitWithAck does not throw on disconnect HOT 3
- Make `emitWithAck` for a room say which socket(s) failed to ack HOT 1
- Connection recovery doesn't work HOT 2
- Allow to bind socket.io to bun built in server. HOT 2
- authToken = null in springboot despite set by the client HOT 1
- Replace `XMLHttpRequest` with `fetch` HOT 1
- "emitWithAck" function leaks memory when acknowledgement timeout HOT 1
- this.children is undefined for ParentBroadcastAdapter broadcast HOT 3
- How to get error details in client when server side with io.engine.use middleware HOT 1
- [adapter]: Add option to fetchSockets that returns results even if some nodes didn't respond HOT 1
- Simplify Socket.Io Docs by Removing `createServer` HOT 1
- What's the path!? HOT 1
- When I send a lot of data, the connection will breaks HOT 1
- Make room name string argument compatible with ES6 template literals HOT 4
- When I sent a byte [], the client failed to receive it. HOT 1
- My client sockets disconnect with a "ping timeout" reason after a few hours of connection and can't connect again HOT 8
- Argument of type '(nsp: any) => RedisStreamsAdapter' is not assignable to parameter of type 'AdapterConstructor' socket.io version 4.7.5 HOT 2
- socket.request.user empty after v2 to v4 migration
- Cannot send an object with more than 2 properties to socketio server from NextJs api
- Getting error websocket.js:39 WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=4&transport=websocket' failed: again and again
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from socket.io.