quick question.
On a Java Sever using Logux Proxy:
Token is not sent with all Actions, only with Auth command once?
When Proxy calls our stateless Rest Backend with an Action (like subscribe, or custom action) how do we know the authentication took place fine?
ps: I'm using Logux Vuex, do I need to manually add the token to each commit.sync( call?
but what about the subscribe, which is done automatically from the loguxMixin
Hello, basic usecase (Logux Vuex, Logux Proxy, Java Spring Boot Rest Backend):
- I use Logux to persist a new object (a Car)
- The DB persist is done async, when it finishes it returns an UUID
- How do I broadcast to all Subscribers that a new object was persisted? and send the object/uuid
ps: I know that a better approach would have been to set the UUID in Vuex, so the RESEND action would have taken care of all this,
but is there a best practice for my scenario?
- Do I send a SEND_BACK REST call from the Backend to the Proxy (as it's done when the user first subscribes to a channel)?
46 replies
@ai Hey! Could you tell me, which strategy you using when need to show a loader for connection to a socket and then use an optimistic update?
My problem: if I go to offline mode, I have an infinite switch between connection and disconnected status and my loader also infinite
My problem: if I go to offline mode, I have an infinite switch between connection and disconnected status and my loader also infinite
1 reply
Vuex includes
isSubscribing key, but it's key to wait when an application will connect to a some channel
Hello!
I've just starting learning about logux. Could you help me to understand one thing?
Initially, I thought that logux is a transparrent wrapper above Redux. I though, that redux actions will be executed locally and logux will send actions to the backend in the background.
I've tried to create a simple example, and I see that, in fact, the actions are not reduced on the client.
Is it by design or I'm missing something?
I've just starting learning about logux. Could you help me to understand one thing?
Initially, I thought that logux is a transparrent wrapper above Redux. I though, that redux actions will be executed locally and logux will send actions to the backend in the background.
I've tried to create a simple example, and I see that, in fact, the actions are not reduced on the client.
Is it by design or I'm missing something?
12 replies
I've tried to follow your official tutorials for both the proxy server and node.js server and in both cases the same thing happens. I get my client and server started and in the browser console i just see a cycle of 'logux state is connecting..' 'logux state is disconnected' that continues indefinitely. Where could I start debugging?
1 reply
the client terminal tab says:
```Compiled successfully!
You can now view client-logux in the browser.
Local: http://localhost:3000
On Your Network: http://192.168.11.5:3000```
but nothing displays on the local address. It only displays on the 'on your network' address which seems odd too.
(also why doesn't markdown formatting of code work - I'm following the help tip)
@ai I'm a little confused about the Logux.io docs. Specifically the Redux API and VuexAPI topics seem to have little content specific to Redux and Vuex and more importantly contain content of general use not covered elsewhere. For example Client, CrossTabClient etc. etc. are only covered in these topics . I would have thought all the content which is Framework independent should have it's own Topic and Redux/Vuex topics only contain info specific to there use.
20 replies
It would be great if logux/undo included the failed action that is being undone. I understand from https://logux.io/guide/concepts/action/#system-actions that:
action.id will be equal to meta.id of reverted action
however that means I need to keep a queue of added actions in order to find the id and know what the action being undone was.
Or am I missing something here?
28 replies
@ai I'm trying to 'Sign Out' the current user and revert back to a guest/anonymous user. I'm doing:
After the
What is the best way to accomplish a Sign Out back to the guest user?
'logux/unsubscribe' and then Client.changeUser( guestUserId, undefined ).After the
changeUser() I get a "logux/subscribe" with resubscribe: true and the original user.What is the best way to accomplish a Sign Out back to the guest user?
3 replies
@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