alexstrat
commented
10 years ago after browserifying/bundling the simudp (dgram-browserify, socket.io always shows up as missing. I have tested everything i coud but developer console shows always the same:
GET http://mnaknmbehfkifpdfihbjplhcjicelfog/socket.io/1/?t=1381705314334
socket.io is not missing at all, since that's socket.io itself that is doing this request.
simudp requires a server part running (that is built on top of a socket.io sever) to work, but I guess you've started it (like described in readme). However, here, socket.io tries to connect to a server which address is mnaknmbehfkifpdfihbjplhcjicelfog: pretty weird for an address, but I guess that's because you are using simudp inside a chrome extension, aren't you ?
To solve that, I guess that's the best you can do for the moment is to specify the server address manually for each instantiation of simudp socket. Try something like that:
var socket = SimUDP.createSocket('udp4', 'localhost:8080'); // if the server is running on 'localhost:8080'However, I'm just realizing that's not totally handy. For instance, when you are using a lib relying on dgram without simudp in mind. I'll try to find a solution for that, probably based on global options for simudp.
i have tried different ways to use the module, like: browserify -r dgram-browserify:dgram -r socket.io-client -o bundle.js
You absolutely don't need to require socket.io-client since it's bundled in dgram-browserify. And I guess that you don't need to -r dgram-browserify:dgram since, based on package name, browserify will understand that it should use dgram-browserify instead of dgram.
as i do set the broadcast flag to true.
any chance to add this in?
i am looking at it but no idea how to help...
It should not be too complicated to add. It might look like something like:
--- a/lib/server.js
+++ b/lib/server.js
@@ -105,6 +105,10 @@ Proxy.prototype.handleBind = function(client, bind) {
});
});
+ client.on('broadcast', function(msg) {
+ udp.setBroadcast(msg.flag);
+ });
+
//bind error events
udp.on('error', function(reason) {
client.emit('error', reason);
diff --git a/lib/simudp.js b/lib/simudp.js
index 726552f..89aa4db 100644
--- a/lib/simudp.js
+++ b/lib/simudp.js
@@ -143,8 +143,8 @@ Socket.prototype.address = function() {
// not implemented methods
-Socket.prototype.setBroadcast = function(arg) {
- throw new Error('not implemented');
+Socket.prototype.setBroadcast = function(flag) {
+ this.sio.emit('broadcast', {flag: flag});
};
Socket.prototype.setTTL = function(arg) {
vanous
Hello, i have been pulling my hair here...
after browserifying/bundling the simudp (dgram-browserify, socket.io always shows up as missing. I have tested everything i coud but developer console shows always the same:
GET http://mnaknmbehfkifpdfihbjplhcjicelfog/socket.io/1/?t=1381705314334
which points to: xhr.send(null); in bundle.js,
created by:
browserify -r dgram-browserify -r socket.io-client -o bundle.js
i have tried different ways to use the module, like:
browserify -r dgram-browserify:dgram -r socket.io-client -o bundle.js
etc. but still the same result. what am i doing wrong?
node.js v0.10.20 simudp 0.0.16 socket.io 0.9.16 browserify 2.34
thank you
Petr
edit: Chromium Version 29.0.1547.57 Debian jessie/sid (217859)
edit2: ok, it seems like it a boils down to
Socket.prototype.setBroadcast = function(arg) { throw new Error('not implemented'); };
as i do set the broadcast flag to true.
any chance to add this in?
i am looking at it but no idea how to help...
P.