NIP52 + Spring WebSocketClient

[avlo]

@tcheeric hi, eric. if of interest/usefulness to you, the following PR (submitted from-and-to my fork of nostr-java) contains a brief overview and alternative nostr client (Spring WebSocketClient atop Reactive Streams) reference implementation.

below video-capture showing execution of all nostr-java tests using spring WebSocketClient (console, left) and nostr-relay events received (console, right) with subsequent "OK" responses sent by relay and registered (asynchronous awaits()) by client.

ApiEventTest.mp4

[tcheeric]

Wow, this looks awesome. I'll take a detour look at it this week.  Thanks -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com 10 Sept 2024, 22:35 by ***@***.***:

…

@tcheeric <https://github.com/tcheeric>> hi, eric. if of interest/usefulness to you, the > following PR <avlo#2>> (submitted from-and-to my fork of nostr-java) contains a brief overview and alternative nostr client (Spring WebSocketClient atop Reactive Streams) reference implementation. — Reply to this email directly, > view it on GitHub <#179>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQMG7F66WGMXNB27LEXYJTZV5Q35AVCNFSM6AAAAABN7UEJNCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGE3DMMZUGE>> . You are receiving this because you were mentioned.> Message ID: > <tcheeric/nostr-java/repo-discussions/179> @> github> .> com>

[tcheeric]

Nick, this looks great. I always wanted to accommodate relay responses but my attempts were always convoluted. I'm still familiarising myself with your pr, and your solution looks very elegant. Thanks.

[avlo]

spring is doing all the heavy lifting in this implementation. a smaller & tighter refactoring (removing manual "sink" management, letting reactive/netty handle them implicitly) will be pushed shortly. it's further easier to understand and will have a cleaner/more-intuitive client API. I'll keep you posted.