You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obviously CapnProro is an inspiration here, but have you given any though to a remote-procedure-call specification? Seems to me like a bunch of inexpensive chips could potentially be networked together (I see you mention PJON) into a greater whole, but a solid remote-procedure-call system would be needed.
Protobufs are probably the main inspiration (I see CapnProto as an
optimization of protobufs). Since RPC mechanisms are built-into protobufs
it was/is certainly a consideration.
I think eventually having a standard RPC mechanism would be valuable and I
think you could do far worse than something similar to Protobufs.
On Mon, Sep 18, 2023 at 8:55 AM traverseda ***@***.***> wrote:
Obviously CapnProro is an inspiration here, but have you given any though
to a remote-procedure-call specification? Seems to me like a bunch of
inexpensive chips could potentially be networked together (I see you
mention PJON) into a greater whole, but a solid remote-procedure-call
system would be needed.
See also the anachro PC <https://anachro.computer/>
—
Reply to this email directly, view it on GitHub
<#1>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKUFS3UY37BL5O3W4E3YSDX3BHGNANCNFSM6AAAAAA44YR6NA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Obviously CapnProro is an inspiration here, but have you given any though to a remote-procedure-call specification? Seems to me like a bunch of inexpensive chips could potentially be networked together (I see you mention PJON) into a greater whole, but a solid remote-procedure-call system would be needed.
See also the anachro PC
The text was updated successfully, but these errors were encountered: