Comments (3)
TL;DR: apps that are purely data driven in realtime. The socket is the channel for live data, the screen components are layout structures for presentation and action-capture only.
I think the most promising use case is flux or 3factor architectures for smart applications where the dynamic information to the screen is based on user, system, global, etc contexts.
I build apps in the asset management and reservations industries. Those apps are like stock-markets and are exposing stateful options for highly contentious user actions. The websocket store lets me avoid polling, sure, but it actually allows me to push changes to reality is a separate channel than the views' request channels. This becomes extremely powerful when a single user may have multiple live contexts into the data and actions (e.g. on multiple devices, IoT controlled/monitored components to their overall experience, 3rd parties sharing their experience in multi-user interfaces)
The neatest story about the use case is from facebook's impetus to create the flux architecture: buggy notifications. https://facebook.github.io/flux/docs/in-depth-overview
3factor: https://3factor.app/
from svelte-websocket-store.
from svelte-websocket-store.
I still don't understand the use tho. Does this require some specialized back end that spits out a specific form of data? I just have a hard time understanding the relationship between generic app events and a store that is supposed to store specific data for access
from svelte-websocket-store.
Related Issues (16)
- Add function to manually reopen socket
- Enable Github discussions HOT 1
- Error on import? HOT 7
- Dev run automatically connects to Node HOT 1
- The following packages did not export their `package.json` file HOT 7
- Support for Gzip HOT 5
- (!) Missing global variable name HOT 1
- Add setup guide for Jest and this library HOT 1
- A new connection is created every time the store is updated HOT 1
- Online status HOT 2
- Suggest drop forced json
- Prep for serverside
- SvelteKit and undefined readyState
- ReferenceError: WebSocket is not defined HOT 3
- Is it possible to use this with non JSON endpoints? HOT 4
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 svelte-websocket-store.