Bluesky Explorer

#Webworker

Latest posts tagged with #Webworker on Bluesky

Trending

#World Baseball Classic #Rachel Maddow #Trump and Cuba #Vaccine Policy #DLSS 5 #Oscars #Strait of Hormuz #Sonic Racing #Ukraine Conflict #World Baseball Classic #Rachel Maddow #Trump and Cuba #Vaccine Policy #DLSS 5 #Oscars #Strait of Hormuz #Sonic Racing #Ukraine Conflict

Posts tagged #Webworker

@migrantx.bsky.social

6 months ago

EAL - Event Abstraction Layer?
EaaS - Event-as-a-Service?
Quantum-Entangled Modules?
DOM-to-WebWorker-to-DOM event bridge?

Never heard of these concepts? Can be true, because we just dropped them on GitHub.

#JavaScript #WebWorker #EventHandling #WebDev #Innovation #JS

github.com/eypsilon/Yps...

1 0 0 0

FunctionalProgramming

@functionalprogramming.activitypub.awakari.com.ap.brid.gy

7 months ago

Preview

The Right Way to Squeeze Out CPU Performance in Web Apps This article was translated, original article here. Browser Thread Allocation Modern...

The Right Way to Squeeze Out CPU Performance in Web Apps This article was translated, original article here . Browser Thread Allocation Modern browsers generally adopt a multi-process archite...

#webworker #programming #javascript

Origin | Interest | Match

0 0 0 0

Lorenzo 'kelset' Sciandra

8 months ago

allright im so close to giving up on this but I'll try; any of you fellas got #webpack5 to play nice with #webworker(s)? I am genuinely feeling I'm losing my mind trying to get it to work properly.

Like: exact same code, in a Vite set up it works flawlessly, in Webpack ❌💀

0 0 1 0

🤷 Nico Martin

9 months ago

#usePipeline is a #React hook that allows you to use the #transformersJS Pipeline function. You can pass a task and a model and everything else is handled by the hook. It even handles the #WebWorker communication so it's not blocking the main thread!

0 0 1 0

@dev.to.web.brid.gy

10 months ago

Preview

Create a Websocket client in Javascript using a web worker This is a short tutorial on how to create a JavaScript WebSocket client that runs in a Web Worker. The finished files can be downloaded at: github ## Introduction: The goal is to exchange data between a WebSocket server and the web client in real time. I decided to use a Web Worker to outsource the handling of the WebSocket data flow from the main thread, to reducing the communication load. I also implemented a reconnection logic, since the connection could not be establish or was closed unexpectedly > We will create two files: > > * **index.html** : _contains the load of the web worker and processing datas from the WebSocket connection_ > * **websocketHandler.worker.js** : _The web worker file, handling of the WebSocket connection and datas_ > ## Short infos to Web workers > A web worker... > > * runs in a separate thread, independent from your web browser's main thread > * cannot access or manipulate the DOM > * communicates with the main thread using messages via "postMessage" > * runs in a separate .js file > ## Creating the Websocket client * Let's start by creating a JavaScript file named **websocketHandler.worker.js** * At the top, we’ll add some variables that we’ll use later let socket = null; // contains the socket object let shouldReconnect = true; // a flag when we want to auto reconnect let reconnectTimeout = null; // contains the reconnect timer let wsServerUrl = '' // the URL to our WebSocket server * Next we add a "onmessage" event function for handling incoming messages to the web worker. onmessage = function (e) { const data = e.data; handlingWebSocket(data); }; This will be triggered when a message sent to the web worker. The format for this messages will be: `wsWorker.postMessage({ type: '<will be connect, send or disconnect>', payload: '<datas of the message>' });` * Create also a function **handlingWebSocket(data);** for processing the WebSocket interface function handlingWebSocket(data) {} * Now in this function, we create a handling of the different incoming messages-types (connect, send, disconnect). For this create a switch-case for the different message-types: switch (data.type) { case 'connect': // Logic to open the connection to the websocket server break; case 'send': // sending a message to the web socket server break; case 'disconnect': // disconnet and do some clean up break; } } Let's fill the different cases. * **Case: connect** - Connect to the Websocket server. When message of type "connect" `wsWorker.postMessage({ type: 'connect', wsServerUrl: 'ws://192.168.100.150:4040' });` is coming to the web worker, we check if still a connection is open, clean the socket object for safty and then call a seperated **connectToWebsocket** function. case 'connect': // save URL in local variable wsServerUrl = data.wsServerUrl // set auto reconnect, so when a connection could not be established it will try to reconnect again shouldReconnect = true // be sure that there is not still a WebSocket server object if (socket && socket.readyState !== WebSocket.CLOSED && socket.readyState !== WebSocket.CLOSING) { return; } // to be save the object is empty socket = null; // call the function to open the connection connectToWebSocket(wsServerUrl); break; Then we create and fill the **connectToWebsocket** function function connectToWebSocket(wsServerUrl) { console.dir("Start connection to WebsocketServer..."); // open the connection to the WebSocket server socket = new WebSocket(wsServerUrl); // event which triggered when the connection has been established socket.onopen = () => { // clear the timeout when the connection was established clearTimeout(reconnectTimeout); // send message to parent function that the connection was established postMessage({ type: 'connected' }); }; // event when a message comes from the WebSocket server socket.onmessage = (event) => { try { const msgContent = JSON.parse(event.data); postMessage({ type: 'data', payload: msgContent }); } catch (err) { postMessage({ type: 'error', payload: "Error at parsing message datas" }); } }; // event will be triggered when an error with the WebSocket interfaces raised socket.onerror = (err) => { postMessage({ type: 'error', payload: err.message }); }; // event which triggered when the connection to the WebSocket server will be closed socket.onclose = () => { postMessage({ type: 'closed' }); // clean up before try to reconnect disposeWebSocket() // check if reconnection should be running if (shouldReconnect) { postMessage({ type: 'reconnect' }); // set a timeout every 5sec for trying to reconnect reconnectTimeout = setTimeout( () => connectToWebSocket(wsServerUrl), 5000); } }; } * We also have to create a dispose function "disposeWebSocket()" to do a clean up function disposeWebSocket() { clearTimeout(reconnectTimeout); if (socket) { socket.onopen = null; socket.onmessage = null; socket.onerror = null; socket.onclose = null; socket = null; } } * **Case: send** - Next we fill the case for sending datas to the WebSocket sever. We check if the connection is still open before we send datas. case 'send': // check if the connection still open before sending datas if (socket && socket.readyState === WebSocket.OPEN) { socket.send(JSON.stringify(data.payload)); } break; * **Case: disconnect** - Finally we create the case for disconnecting from the WebSocket server. We call this when we leave the page or the communication should be ending. case 'disconnect': // prevent auto reconnect when the connection was active closed shouldReconnect = false if (socket) { // we call the close method and pass a status code. // code 1000 means normal closure socket.close(1000, "Client closing connection"); console.dir("Sent CLOSE-connection request to server"); } // call the dispose function to clean up disposeWebSocket(); // set the command to end up the web worker semselfe self.close(); break; ## As next we'll create the logic for using our WebSocket web worker * First create the **index.html** file with a default base structure like this: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>WebSocket Worker Demo</title> </head> <body> <h2>WebSocket Worker</h2> <div id="status">Connecting...</div>  <button onclick="sendDatasToWss()">send datas to WSS</button> <script> // here we palce the logig for the websocket interface </script> </body> </html> * Inside the "srcipt" tag we start with create the web worker object const wsWorker = new Worker('websocketHandler.worker.js'); * We use the object and send a postMessage of type: "connect" to call the web worker to connect to the WebSocket server like this: wsWorker.postMessage({ type: 'connect', wsServerUrl: 'ws://192.168.100.150:4040' }); * Then we add a handling for messages from the web worker wsWorker.onmessage = (event) => { const { type, payload } = event.data; const statusEl = document.getElementById('status'); if (type === 'connected') { statusEl.textContent = "#### CONNECTION to WebSocketServer ESTABLISHED ####"; } else if (type === 'data') { console.dir('Data incomming: ' + JSON.stringify(payload)); } else if (type === 'error') { statusEl.textContent = "Error: " + JSON.stringify(payload); } else if (type === 'closed') { statusEl.textContent = "WebSocket is closed"; }else if (type === 'reconnect'){ statusEl.textContent = "Connection to WebSocketServer closed - Try to reconnect..."; } }; * We also add a function to test the sending of datas to the websocket server function sendDatasToWss(){ console.log("Sending datas to WSS"); wsWorker.postMessage({ type: 'send', msgContent: 'SomeDatas you need in the WSS' }); } * Do a clean up when the page will be leave window.addEventListener('beforeunload', () => { wsWorker.postMessage({ type: 'disconnect' }); // Give the worker time to clean up before terminate the web worker setTimeout( () => wsWorker.terminate(), 10); }); When we now open the **index.html** file and the WebSocket connection should be established. We see what's happening in the `<div id="status">Connecting...</div>` on the page.

0 0 0 0

@chopsueey.bsky.social

1 year ago

An illustration of two cogwheels with the labels: 'Main thread' and 'Web Worker'.

An illustration of two cogwheels with the labels: 'Main thread' and 'Web Worker'.

What is a Web Worker?

Web workers are a powerful feature in #JavaScript that allow you to run scripts
in the background, separate from the main thread of your web application.

developer.mozilla.org/en-US/docs/Web/API/Web_W...

#webworker #webdev #performance

2 0 0 0

10 years ago

"Wie alt bist du?"
"Ich hab Flash schon als Murks gehalten, als es noch hip war."
"Ach du sch...!"
#Webworker

0 0 0 0

@paulgreg.bsky.social

11 years ago

WebGL in Web Workers, Today – and Faster than Expected!

WebGL in Web Workers, Today – and Faster than Expected ! blog.mozilla.org/research/2014/07/22/webg... #awesome #webworker #javascript #mozilla

0 0 0 0

@paulgreg.bsky.social

15 years ago

Having fun building my HTML5 slides for #valtechday event with HTML5/CSS3/JavaScript & nodejs #valtech #nodejs #webworker :)

0 0 0 0