import { Server } from '@logux/server';
// fake http to avoid Logux on server /
const fakehttp = { on: (event, cb) => console.log('FAKE HTTP: ', event, cb) };
const logux = new Server(
Server.loadOptions(process, {
subprotocol: '1.0.0',
supports: '1.x',
root: __dirname,
fakehttp,
}),
);
logux.ws = new WebSocket.Server({ noServer: true });
// hack to http
http.on('upgrade', (request, socket, head) => {
logux.ws.handleUpgrade(request, socket, head, (ws) => {
logux.ws.emit('connection', ws);
});
});
// apply server module
logux.listen();
INFO Client was disconnected at 2021-01-26 21:33:42 but there's no call from Proxy to Backend to inform that this happened. I need to do some cleanups on the Backend when a user disconnects. Is it possible? 10x
16 replies
cosminv6u but I can't log in with github ... so i used gitlab
Hi! I'm very very new to logux (have only read the doc so far) but it looks awesome. I have a tricky use-case and I'm wondering if it fits logux. Basically I want my main server to have all the state, but hide some informations to clients, so the clients would have a different state. So I want client A to send an action to the server, but have the server send a different action to client B, one that hides the information I don't want client B to know about.
Is that something possible? If so how would I go about it? Send a new action in the action's "process" callback?
4 replies
Hi, when using Vuex, is it true that when there's an UNDO (no matter on which fragment of the Vuex store), all actions from the Client Session are replayed (except the failed one) and similarly, when you Disconnect and Reconnect, all actions since the Client Session was created, are replayed?
ps: when I say Client Session: I mean when you access the page (via GET) or you do a refresh
3 replies
disconnected event on the server and then send back some action to all channel members. But it looks like the event object doesn't contain information about client channels. Or maybe I'm missing something and there is another way of doing such things? Thanks in advance
5 replies
Hello.
I'm trying to understand the subscription/resubscription logic.
Could you refine the moment about meta.channels on the client side. https://github.com/logux/client/blob/64c7e442de0e7ccca2372c68c8877d82960796f1/client/index.js#L136
How client can get channels from the server if server cuts all meta except pointed in ALLOWED_META? Cut on server side happens here https://github.com/logux/server/blob/90bde83d65a9efad731395b8ea6f74448933a4b0/server-client/index.js#L175
5 replies
Hi! I have a high-level question.
Let's say I have an action with a slow "process" function. If that action is followed by a second action that is faster to "process", I could effectively see the effects of that second action before the first one, correct?
Since my redux client is processing the actions synchronously, this could mean that the (effective) order of actions could be different on the server and the client?
And this is what the following ticket is about, correct? logux/logux#54
65 replies
11 replies
LoguxError: Logux received an invalid credential error (bad credentials). It sends the same message if authentication fails.
2 replies
Hi guys!
I am working on a project where we have this Main App that consumes a React Component's subtree from our own private Components Library. In a modular microfront-end kind-of way.
Just for extra clarification, the Components Lib exposes a subtree that will be consumed by the Main App. Each (the Main App and the Components Lib) have their own Redux store.
What we are trying to achieve here is having both Redux stores in sync (actually just some State slices), even-though both Stores are always working in the same Tab.
Is there any trade-offs for using Logux model? To me, each app will have its own Id and will communicate through Logux proxy. So, I feel it might work. But, since I heard Andrey many times talking just about cross-tab communication, I wanted to be 100% sure.
4 replies
@ai The app I've been working on for ages no longer authenticates with the Logux Server. Everything was working fine yesterday and then it broke. I've gone back to an earlier set of code from a week ago and same issue. I've updated logux client & server and restarted Windows twice and same problem.
So far I can't work out why it's broken. I've tried FF, Edge and Chrome - same issue.
I almost suspect this was an issue waiting to happen, but going back to earlier code has the same problem. I'm not aware of a Windows update yesterday.
I'm just reaching out in case you happen to be aware of something breaking recently.
Ok, I think I may have found the problem. Each User needs to have their own Logux Client Log. I need to create the CrossTabClient before I can talk to the server and get the Users ID etc. And I need the Users ID to identify the users IndexedDb store - new IndexedStore( userId ).
So I have a catch 22. ie. I need the userId to instantiate the CrossTabClient but don't have it yet.
I hope that makes sense.
Trying to use redux with Vue but @logux/redux has the react peer dependency (uses createElement, useEffect hook from react, etc). This seems a bit counter-intuitive, to have logux/redux depend on react, which makes it impossible to use redux + logux + vue. Is there any hack I can use to make this work? Shouldn't logux/redux be more library independent and not couple with react, since redux can be used independently as well?
Thank you!
18 replies
I have a number of scenarios where server.auth() can fail, other than incorrect credentials. For example a database issue. I need to report the specifics of the failure back to the client so the user has detailed info about the underlying issue. Is there any way to do this?
Related to this is the need to fail server.auth() otherwise the client will immediately start sending its Log to the server which can't be processed because of the database etc. issue. I can't see any way to prevent the client from sending it's log to the server once a connection + auth is established?
6 replies
Is there a way for a CrossTabClient to find out if there are other CrossTabClient instances (Tabs) for the same client?
What I'm trying to find out is when does the last CrossTabClient close for a client, so that I can release resource for that client on the server.
Does the server need to keep track of each CrossTabClient instance and use server.on( 'disconnected' ) to see when they have all disconnected?
6 replies
CrossTabClient where I have two Tabs open to the same client. I Sign out of both Tabs which does CrossTabClient#destroy() in each Tab. Both Tabs are still open in the Browser.Then when I sign in
startElection() -> getLeader() returns a clientId from localStorage which can be the other Tab, in which case the Tab I'm signing in never becomes the leader and never connects to the server.
9 replies
Is there any reason not to support Node V15?
4 replies
My conclusion is when you have multiple tabs open then disconnect them
onStorage() is still called after destroy() -> window.removeEventListener('storage', this.onStorage) has been called.This in turn calls
watchForLeader() -> startElection() even though all tabs are disconnected.This in turn cycles through changing
localStorage - leader value and then depending on where the cycle is connecting a Tab can see 'follower' and never connect to the server.The solution to this needs someone with a better understanding of the code than I do.
4 replies
LoguxError: A timeout was reached (20000 ms)
at FilteredNode.syncError (file:///c:/webapps/clibuNotes/node_modules/@logux/core/base-node/index.js:225:15)
at Timeout.<anonymous> (file:///c:/webapps/clibuNotes/node_modules/@logux/core/base-node/index.js:253:12)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7) {
type: 'timeout',
options: 20000,
description: 'A timeout was reached (20000 ms)',
received: false,
connectionId: '31'
}
Server options to allow for a setup with multiple servers for redundancy
2 replies