disgusting terrsts of foreign gypsies foreign terrorst grp/cult

 hey turns out I had not needed to compile that specific websocket library. or might need to. 

would check if websocket implementation in this webrtc implementation is feature complete. 

hmm if i want to use socketio I would need to change to that websocket library. 

yep. 

I think would be required. (i mean socketio) (to ease the logic on server side)

gosh so tomorrow's task is to integrate the socketio client websocket to this webrtc library implementation. 

then afterwards null system and unreal's network code needs to be throughly read to modify the null system there to communicate through webrtc data channel and push the messages to 127.0.0.1 server socket there which would be the replication/network manager stuff's url given by null system. so something like 

- battle listen server: 

 -- unreal network manager server runs on 127.0.0.1 + null system has a inherent udp client (n many, per each battle partici;pant) that pushes to this server + and  per each such client a webrtc connection where the remote' side's actual data i sreceived with a webrtc endpoint here

-- remote endpoint : unreal network pushes the messages to 127.0.01 (replication stuff) + null system listens it there and pushes the messages to above listed server's webrtc connection per this client

then also there is the null protocol's messagings and also logic of battle setup system through this node.js side and respective webrtc/server/client mechanisms spawning of.

so a very complex modification this changing null online system to somewhat webrtc wise communicated. 

hmm but i think tomorrow or following day I could complete. 

i mean very basic initial version. where a socketio redis adapter version holds all redis alike battle room logic. (for signalling layer only) actual communication as goes from udp of webrtc based maintained connection.