Re: Delegation is the Cornerstone of Civilization: Sharing in Sandstorm.io
Kenton Varda <[email protected]> Thu, 7 May 2015 13:07:49 -0700
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CAJaLmO6_T02d9gxby7Yb4sjVe428rDAo3tnz+B5HkDkwCfOR9g@mail.gmail.com> |
Hi Tim, On Wed, May 6, 2015 at 1:23 PM, Tim Coote <[email protected]> wrote: > The delegation ucs are very much what I’ve got in mind for IoT based > applications, where T’s can be composed up (and are mostly s/w, rather than > bits of silicon). How well does the sandstorm model distribute (so that I > can delegate access to Things that need to be on one computer for Things on > another?) > Well, the sharing model described in the post applies to Sandstorm applications running on a Sandstorm server, so may not be directly applicable to IoT. That said, Sandstorm is based on the Cap'n Proto capability transport ( https://capnproto.org), whose design is based heavily on CapTP. Sandstorm apps talk to each other and to the platform via Cap'n Proto, and at some point they will be able to speak Cap'n Proto directly to external servers or devices. We further are building a powerbox-style UI allowing the user to move these capabilities from app to app. What this means for you is that if your T's use Cap'n Proto to communicate in a capability-based manner then they should be especially easy to integrate into Sandstorm, so that a user can use Sandstorm apps to manage their devices in a capability-based manner. I think this would be pretty awesome -- IoT desperately needs a way to manage devices that doesn't involve ceding all control to centralized SaaS services. -Kenton _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk