Does WL still load a count query into memory and do an [].length lol?
Saw a thread on Reddit about that but it was for v0.9
WRoot chat lol
joshuaandrewhoffman
@joshuaandrewhoffman
Lol... What were you wondering about the socket stuff @mikedevita ? This is an area I've spent a lot of time struggling with and learning. Would love to pay you back for your help the other day
Mike DeVita
@mikedevita
@joshuaandrewhoffman ive got it working i think
working on something else and cant switch back
joshuaandrewhoffman
@joshuaandrewhoffman
Right on. Glad you got it going. Lmk if you snag on anything else or just wanna talk shop spot about redux with sockets
-spot
Mike DeVita
@mikedevita
ok sure
joshuaandrewhoffman
@joshuaandrewhoffman
RIP phones w/ keyboards D:
Mike DeVita
@mikedevita
yeah i hear ya on that one lol
Jason Shin
@JasonShin
davezuko/react-redux-starter-kit#1078
Hi, I have created an issue.
Please have a look, thanks.
Jason Shin
@JasonShin
Wow, Webpack is bugging me so much
Every 5 min, Webstorm freezes
Any recommendation guys?
Mike DeVita
@mikedevita
@joshuaandrewhoffman how did you handle socket updates from other emits like another user updating something or emitting something
I'd assume like if I had an items store in redux when it's updated no matter where or what page I'm at I want it to update
Mike DeVita
@mikedevita
With all connected clients like ... socket.on(item-update... update the items store with the changed item with id..
joshuaandrewhoffman
@joshuaandrewhoffman
So this is where this type of development gets really interesting to me. I'm not convinced there's aa single right way for every app to do this. In my case the sockets are often emitting actions which apply to at most two users: the user who initially sent the action to the server, and the user in the same game room.
So what I did was sort of scope down my concept of state on the server to those rooms and who was in them, and just emit to that. I had trouble getting socket.io's native rooms feature to emit to the calling user, and I had trouble with the automatically created room for the socket ID, so if you figure out the incantation for that please lmk
_
Mike DeVita
@mikedevita
okay
let me give you some background
im building a realtime infrastructure app
joshuaandrewhoffman
@joshuaandrewhoffman
I ended up just rolling my own room tracking since it wasn't terribly complex and I didn't want to be stuck
Mike DeVita
@mikedevita
to manage 300+ virtual machines, with agents on each system that report things like cpu/disk/memory usage and offer an entry point to shutdown/start services in an order on each VM.. for example shut down production ECC instance, which will first shut down the app servers, then the load balancer, then the database.
and i also want to provide realtime updates for things like changes to server info by a user/team member..
right now its not realtime, you have to refresh to see the changes.. the concept is if user a is on the site, user b changes a server i want user a to get notified of the change and see the changes.
i have the agent stuff down, using sailsjs for the backend and socket.io for the connections that works fine.
im just not sure how/where to put the socket.in('server-update, function() .... code at. should it go in a reducer/store file and just dispatch a thunk action like SERVER_UPDATED
joshuaandrewhoffman
@joshuaandrewhoffman
I probably should've checked first, are we pure socket-io here or using socket-io-redux? (Unsure I have that package name right I don't have my code in front of me)
Mike DeVita
@mikedevita
well its sails-io-js which is a wrapper around socket.io
pure socket.io on the client side for now i'd say
but im open to a library like socket-io-redux
joshuaandrewhoffman
@joshuaandrewhoffman
And I'm assuming either way you're doing redux or something redux-like on your server to track your state