Scott Wilson

> A thought: one way you could justify extending existing commands is via the `/version` command. A client could query the server's `/version` immediately after connecting and use the response...

> i think this is a misunderstanding of @scztt 's point. Not at all. I know what he's saying. >a FS `exists` API call is useful because occasionally the mere...

> could another solution be to create the node immediately in a paused state and then defer running it? Thanks, though I think we already have something better than that....

Thanks for your comments @brianlheim. No worries, and sorry if any of this seems impatient. :-) On balance, on looking at this and the /s_query proposal, I think my preference...

> i don't have any issue with that, seems like a good idea to me. :) Ta! @josiah-wolf-oberholtzer should we start a new RFC about this? > I meant n_query;...

I'm not so sure about the semantic drift of this. A NetAddr broadly models a particular endpoint, not a connection. (I admit it's slightly messy, but I'm not sure we...

> So for now having just the port and/or some other attributes would be nice. I'm totally sympathetic to reluctance to add a lot of stuff just to get a...

Just to echo @prko that it's great you've put so much work into this, and even if it doesn't go forward, I hope it's at least been useful in developing...

I think we need to test across a variety of use cases for performance and stability. Large sclang data arrays are not typical usage, and mostly we're prioritising realtime safety....

> Wonder if it is possible to add some bookkeeping to the internal allocater(s) so they can check their memory is being addressed properly? Some discussion and unmerged work here:...