@aphyr Sure, if HTTP is a good choice, depending on needs.
-
-
Replying to @kellabyte
@kellabyte Yeah. I prefer to avoid HTTP because it imposes so much per-request overhead, and most clients don't pipeline well.1 reply 0 retweets 0 likes -
Replying to @kellabyte
@kellabyte replace http-server with tcp-server above, remove :body wrappers, and throw in a null separator.3 replies 0 retweets 0 likes -
Replying to @kellabyte
@kellabyte not that it helps in .net, but https://github.com/ztellman/aleph is pretty darn cool.1 reply 0 retweets 0 likes -
Replying to @kellabyte
@kellabyte gotcha--and I totally agree, there *should* be a fast, simple, broadly used RPC mechanism by now! Everything out there sucks! :(1 reply 0 retweets 0 likes -
-
Replying to @bascule
@bascule@kellabyte says the man building celluloid ;-)1 reply 0 retweets 0 likes
@aphyr @kellabyte my RPCs are broken too! ;) Fortunately the rest is fully async...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.