You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attached file is from JMAP Push get. All from one client(device).
It shows three problems:
Multiple duplicate deviceClientId.
This ID (device + app + time) is supposed to be unique, so it should also be enforced as unique on the server.
The JMAP entry doesn’t have a timestamp, making it impossible to determine which entry is valid for subscription checking.
There seems to be no cleanup process.
Many entries have expired but remain in the system.
For the client UI, it would be better if, after a few retries (e.g., 30 seconds) to the JMAP proxy server, the entry disappears, indicating an error.
What happened?
Implementing JMAP push against stalw.art.
Attached file is from JMAP Push get. All from one client(device).
It shows three problems:
Multiple duplicate deviceClientId.
This ID (device + app + time) is supposed to be unique, so it should also be enforced as unique on the server.
The JMAP entry doesn’t have a timestamp, making it impossible to determine which entry is valid for subscription checking.
There seems to be no cleanup process.
Many entries have expired but remain in the system.
For the client UI, it would be better if, after a few retries (e.g., 30 seconds) to the JMAP proxy server, the entry disappears, indicating an error.
PushSubscription-get.json
How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
Version
v0.11.x
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
None
What operating system are you using?
MacOS
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: