the enostr stuff is old and crufty. i was working on a networking side of nostrdb at one point but it fell by the wayside for the time being
Discussion
Very helpful. Thanks for explaining!
the main point of enostr/nostrdb_net is to avoid parsing json twice, enostr basically just barely and badly parses some high level tokens (OK, EOSE, AUTH, etc, subscription ids, etc) without parsing the json. then it passes the websocket &str directly to nostrdb for processing.
Also extremely helpful! Makes a ton of sense.