Hello,
I want to use Logux at work and I have some questions about the best practices.
Up until now I played with Logux testing various scenarios, but now I want to use it for real.
My usecase:
I have a list of car stores that's displayed in the screen (paginated, sortable, filterable).
The list is populated at first via Excel File Upload.
After that you can retrieve all stores, change various fileds of a store, delete one, delete all.
My Questions:
- Should I use Logux for FileUpload? Or just REST? [I'd say no]
- Should I use Logux for retrieving the list (findAll)? Or just REST? [I'd say no]
- Should I only use Logux for updating/deleting one Store, nothing more? [I'd say yes]
- Should I send 1 Logux action per each field of the store that is changed? Or send all fields at once in 1 Logux action? [I'd say 1 action per field]
- We have a Java + Spring Boot + Axon Backend.
Now we use Logux Proxy which calls a REST Endpoint in Spring (created by me), then this Endpoint sends Axon Commands.
Could we skip the Logux Proxy and have the Logux Vuejs or Logux Vuex talk directly to Axon? Knowing that both Logux and Axon implement CQRS?
21 replies
Hello. First off, amazing project. The entire offline-first, optimistic UI approach is, frankly, awe-inspiring.
I have a question regarding your suggestion for server-side actions from a few days ago. This one:
async load (ctx) {
let messages = db.findMessages({ room: ctx.id })
return messages.map(i => [{ type: 'message', text: i.text, authorId: i.authorId, room: i.room }, { time: i.createdAt }])
}I've added something similar to my project, but the problem is that the ordering of actions with identical timestamps is non-deterministic. Reloading the client multiple times produces different results.
I believe it's because Logux server processes each of the returned messages asynchronously, and the logical timestamps for the same createdAt are assigned in whatever order the promises happen to execute.
Do you have any idea how I can have same-timestamp messages preserve ordering when reloading? I've tried setting meta.idof the original client for returned messages (since it includes the counter), but that made the original client ignore the messages on reload.
54 replies
in response to the thread above:
all other clients produce normal debug, something like:
Logux added map/editMap action
index.js:25 Action {type: "map/editMap", payload: {…}}
index.js:25 Meta {id: "1592942048725 clientIdTodo:WBhtspbq:yc8TcHMd 0", time: 1592942048725, reasons: Array(1), added: 2}
index.js:23 From: clientIdTodo:WBhtspbq:yc8TcHMdthe original client sees this:
Logux action 1592942048725 clientIdTodo:WBhtspbq:yc8TcHMd 0 was processedso just the ID
12 replies
Я понимаю, что идеологически, мы хотим добиться автономности, но у меня возникла потребность создавать сущность, получать её идентификатор, и продолжать с работать этим идентификатором. ID должен быть уникальным среди всех пользователей.
У меня есть решение: генерировать ID с помощью uuid на клиенте и продолжать работать. Но мне не нравится такой вариант потому что, ID будет участвовать в образовании URL и во первых может сложится ситуация, когда URL будет сгенерирован до того, как фактически сущность будет создана на сервере, второе, id может оказаться не уникальным и в этом случае я думал отправлять с сервера новый id и обновлять сущность но, url в такой момент изменится, а пользователь мог скопировать и использовать старый URL, который оказывается не валидным или ведёт в другое место.
22 replies
@ai I'm trying to understand the async/sync nature of server.type( 'SOME_ACTION1', { process()... } calls on the Logux Server.
I've tried async process(){ await dbUpdate() } however 'SOME_ACTION2 -> process() is called before 'SOME_ACTION1' -> process() completes.
I'm only looking for clarification, not reporting an issue or wanting anything changed. If I'm correct and actions fire asynchronously and can't be made synchronous then I need to queue them up so that I can process them in order and to completion.
15 replies
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
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
isSubscribing key, but it's key to wait when an application will connect to a some channel
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
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.
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
'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
dispatch.local() looks like what you want. See: https://logux.io/recipes/cross-tab/
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
});
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
15 replies
5 replies
