Andrey Sitnik

Promotion

7

The long-term plan of Logux Django promotion - [ ] Add engine to the real project - [ ] Add docs to Logux Django `README.md` about Logux benefits for Python...

We need to add stream support to protocol processing as [it requires in docs](https://logux.io/protocols/backend/examples/#subscription). Pseudocode: ```diff - answers = [get_resend(), get_access(), get_processed()] - response.send(json: answers) + response.write("[") + resporce.write(get_resend()) +...

Хороший новости — наконец-то у нас есть спецификация протокола между бэкендом и Логаксом: https://logux.io/protocols/backend/spec/#action Плохие новости — протокол пришлось обновить. Один парень нашёл, что наш старый API (когда клиент выставляет...

Wrong output on unkown channel

3

If Logux sends `{ type: 'logux/susbcribe', channel: 'unknown' }`, Rails will answer: ``` Write to Logux response: ["unknownChannel","1554484116313 380:R7BNGAP5:Pjoz3bdE 0"] Write to Logux response: ] ``` But Logux wait for...

Strange behaviour

3

I am adding `prices` channel to Amplifr. Gem force me to have some code for the channel. So I created `app/logux/channels/prices.rb` with: ```rb module Channels class Prices < Channels::Base end...

Remove Amplifr’s methods from `Action`

1

`Logux::Action` has few methods, which are not part of Logux core: `action_name`, `channel_name`, `channel_id`. Let’s remove them since we should not copy Amplifr-only methods to core system.

- [ ] https://github.com/logux/examples/issues/8 - [ ] https://github.com/logux/examples/issues/6 - [ ] https://github.com/logux/examples/issues/11 - [ ] https://github.com/logux/examples/issues/14 - [ ] https://github.com/logux/examples/issues/7 - [ ] https://github.com/logux/examples/issues/10 - [ ] https://github.com/logux/examples/issues/12 - [x]...

Docker docs

2

How to run Logux server in Docker with `Dockerfile` example

Avoid timeout error on long processing on client/server

1

If we have too many work on server or client, connection can be lost because of ping timeout. Need to investigate the problem deeper and find a best solution.

`` is useful only for data loading, but not for server errors during data changing. Also, it is not flexibly for custom stores which use `useStore()`.