@BorisChumichev I'm not a Redux user but from the docs
dispatch.local() looks like what you want. See: https://logux.io/recipes/cross-tab/
@ai I'm confused about the Login process using your example https://logux.io/recipes/authentication/#method-2:-everything-in-logux
After the client gets
When I do this and then do a
The only way I've been able to get the login changing from the anonymous user to the real user is to
After the client gets
'login/done' I assume client.changeUser( action.userId, action.token ) needs to called to change from anonymous to the logged in user.When I do this and then do a
logux/subscribe the client is in a incorrect state as it still has the anonymous login which hasn't received alogux/sychronized leaving setSynchronized() in status() never passing if (Object.keys(processing).length === 0) because it has the anonymous item still present. Apologies for the long winded explanation.The only way I've been able to get the login changing from the anonymous user to the real user is to
client.destroy() and then client.start() with the logged in users credentials.
3 replies
const Logux = createLogux({
subprotocol: config.subprotocol,
server: config.loguxProxy,
userId: someUserId
token: i-want-to-change-this-when-user-pushes-a-button
});
Hi! Related to the Server Proxy, isn't the idea that it knows how to communicate with a Logux Client, and then we implement some mappings in the Proxy so that it also knows how to communicate with the legacy backend? Acts like a bridge so that we don't have to bring any changes to the legacy backend?
Currently the documentation suggests to use Django or Rails library or implement your own inside the legacy backend, which makes me wonder why not then use that library to communicate directly with the Client?
Currently the documentation suggests to use Django or Rails library or implement your own inside the legacy backend, which makes me wonder why not then use that library to communicate directly with the Client?
4 replies
@ai You might be interested in https://twitter.com/mikeal/status/1289655954443706368 I can't DM you on Twitter.
To explore logux, I have built logux synchronization with auth on top of redux example todo app, might be helpful for someone: https://github.com/ambientlight/logux-todomvc
It also seems like Logux Data may not have a suitable text type initially — vs Yjs and Automerge, which seem to have working ones.
For the text type: My questions are whether I should wait for Logux Data (if it's a few weeks, or?) or try to find a way to use Automerge's CRDT with Logux — is that even feasible?
For the node tree: Would I be able to use Logux Data to model a tree of nodes?
I would also like to materialize some views, to index some data, on the client — could Logux do this, or help me keep those views up-to-date?
15 replies
I also had a question on how you think about the cross-over between full-history-saved-by-CRDT vs only-last-state saved. It seems like we want history to be able to do optimistic updates, merging, offline, sync, but it's also unreasonable to store all history for all time. So I think in practice we'll have to have both. So there should be some kind of design decision where that boundary lies, and perhaps configurable some way. For example, design a system that will "finalize" state after T amount of time, but allow any kind events to "rewrite history" until T time has passed? I just haven't seen anything like this — in Logux it seems to be the server that finalizes state when it sees events, or?
5 replies
@ai When a client comes back
I need to know this so the server db is updated before I get the server to send the client it's updates.
online and has a log of updates to send to the server, how can I find out when they've all been sent. This is all handled y Logux client code and I can't see how to see what it is doing.I need to know this so the server db is updated before I get the server to send the client it's updates.
2 replies
Around each 40 seconds
I restarted the Logux Proxy Server and it behaves the same
Doesn't matter on what page I am so I think the reason is not bad code
Maybe a network issue 🤔
12 replies
Hey, guys! I try to build a simple app with rails backend but faild with this. The connection from client goes to proxy and rails well, but when I try to add something to logs proxy does not receive any message.
I suspect that client does not send action to server. What I did wrong? client send action code below
loguxClient.log.add({
type: 'question/pick',
payload
});
Guys, what about auth for logux-rails+devise? Do I need to implement JWT and use it like I saw in example https://logux.io/guide/concepts/node/#authentication or you have 'in box' solution for devise somewhere?
3 replies
I've got an issue with client Log entries being ignored. Here's the steps:
1) Client is offline
2) Client does CRUD actions which are added to the log.
3) Client Signs Out of app.
4) Client Signs In to App and connects to the server.
4a) This does log.add( { "signin" } with user = "anonymous" which is added to the log.
4b) Client connects to server, auth is done and client does
4c)
1) Client is offline
2) Client does CRUD actions which are added to the log.
3) Client Signs Out of app.
4) Client Signs In to App and connects to the server.
4a) This does log.add( { "signin" } with user = "anonymous" which is added to the log.
4b) Client connects to server, auth is done and client does
syncSince()4c)
syncSince() -> syncSinceQuery() -> outFilter() matches the "anonymous" signin log entry and discards the earlier unsent crud log items.
15 replies
Привет! У нас есть клиент (Vue) и сервер (nodejs) на logux, сервер работает с PostgreSQL. Помимо logux сервера есть административная панель с SSR на php, которая работает с той же БД. Мы столкнулись со следующей проблемой: нам нужно по изменению, например, ролей пользователя, из административной панели отправить сообщение в channel. Похоже, что выходом будет поднятие вместе с logux сервером на nodejs рядом http сервера (express) и принятие сообщений от PHP событий и отправка их в logux channels. Подскажи, есть ли возможность вне описания экшнов и каналов отправлять экшны в каналы (например, из обработчика express)?
4 replies
And what's logux-data? (issue #11)
5 replies
Hi. It seams that logux is exactly what I was looking for. :) Great work I have to say - congrats! Can I use logux with angular? I already use a state tool (aktia) - Can I combine them? Is there any example server and client? I need to connect to php rest api (as backend) via server - is this doable. Are there any other projects like logux? So many questions :) I hope you can help me there - thanks
19 replies
Привет! Обнаружил проблему с рассинхронизацией после обрыва интернета. На фронте есть subscribe на channel сущности (character), load (на сервере) которого отдает всю сущность целиком. Последовательность такая:
- Отключается интернет
- Выполняется действие - добавляется action (
setRaceChoice), который меняет одно поле данной сущности - Включается интернет
- Одновременно отправляются 2 запроса - отправка
setRaceChoiceи подписка на channelcharacter - Соответственно,
setRaceChoiceне успевает обработаться до того, как прилетает load от channelcharacter- и приходят устаревшие данные
Используется NoSQL БД - нормальную блокировку сделать проблематично
WS лог выглядит так - http://prntscr.com/us7lok
Есть ли возможность это решить?
7 replies
Hello, I've run into a problem and I'm not sure if it's a known bug or some issue with my own code:
- Client is offline and subscribed to the "groups" channel.
- Client updates an existing group (
add_groupaction, stored locally for now). - Client reconnects.
- Server processes
add_group- but it takes a while (async DB query). - Server sees client's subscription and sends
add_groupactions for groups (in the channel's load function) - Server finishes processing the client's
add_groupmessage.
Because the DB query hasn't finished yet step 6 sends outdated group information. This seems to happen no matter whether my load/process functions are async or not. Is this what's being addressed by logux/logux#54
4 replies
Hi, I'm coming back with an old issue we have. We use Logux Proxy and expose Rest Endpoints using Spring Boot Java. We want all the incoming rest requests to contain the Auth token we send from UI. This token is sent with the AUTH Action, but it's not sent with subsequent actions. Putting a firewall and whitelist the Logux Proxy is not an option because in that token we have more data, not only for authentication. We use Logux Vuex. Can we somehow intercept the outgoing WebSocket Messages and add in the meta the token? I don't want to use vanilla JS Logux, as I like Logux Vuex. I think it's a very common requirement for Spring Boot, so it might be helpful. I can help with the Logux code if you want.
85 replies
It would be nice if you can give us a small guidance of what needs to be done. Right now we're using the documentation and we reverse engineer the JavaScript code, but it's a little bit hard for us.
I know we need to take care of each nodes time, put logs in order and so on. Maybe we can create on gitter a separate channel and have a longer discussion
7 replies
Hi, is it possible to change token on the logux client without changing user? Let's say I have an authentication token, that is about to expire, and I want to refresh it and replace it on logux client. I found only
changeUser user method, that I might use, but I don't want to disconnect/reconnect, etc.
14 replies
- Server state is what you have in your database. Nothing more. And I think, after server crush, client will save all actions in the log, that will be processed after reconnection.
“Logux is based on the offline-first idea. If the node is offline right now, new actions will wait for a connection in the node’s log. Offline is a standard mode for Logux application.”
- Logux Server Pro: https://logux.io/guide/architecture/parts/
My backend is NodeJs, I implemented increment and decrement (the Counter) example.
When I test it manually it works fine. When I run each testcase individually it works fine. But when I run all 8 test cases, sometimes they fail, always different, there's no rule.