Filters are based on polling even when connected via Websocket, right? #1432
-
I really like the functional API for filters. However it seems like event filtering is accomplished via polling in the background. It's not instantly push based, even when I connect to a node via Websocket. For example this one fires every ~5 seconds instead of popping up instantly when a new block is added: web3j.blockFlowable(false).subscribe(block -> { Or did I miss something? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Yes, is this still polling, subscribing to new blocks is supported in WebSocketService; here is an example |
Beta Was this translation helpful? Give feedback.
Yes, is this still polling, subscribing to new blocks is supported in WebSocketService; here is an example