David Whittington
David Whittington
@rixcian Hey, just wanted to say thanks for this well written ticket! The team is in general agreement that there's a need for something like this, and the details seem...
@rixcian Great! We'll spend a bit more time digging in and get back to you with some design questions.
Alright, first off, minor quibble. :laughing: > Currently, there is no real-world use for indexed data in the database; this feature would finally give indexing some meaning You do know...
> { "method": "", "event": "", "params": "
> - Use of redis (or [dragonflydb](https://www.dragonflydb.io/)) in-memory db for storing subscription IDs and params or use just own implementation of some structure? For single node, in memory data structures...
I'm also curious if you've considered the pros and cons of implementing our own websocket protocol vs using something like GraphQL subscriptions.
> // Our possible usecase, not important for overall discussion, but might explain why it's good idea. Definitely important to hear uses cases! > LMK if you want PR with...
@angrymouse Yes. Assume that we have N ar.io nodes and the actual websocket can be connected to any of them. What's the architecture for streaming updates and maintaining subscription state....
@t8, I'm interested in hearing more details about your use cases if you can share.
@angrymouse Do you mean unbundling, tx processing, etc. would only be streamed to the clients connected to the writer in a multi-node setup?