inicio mail me! sindicaci;ón

E, episode two (Birdview on remote objects)

Just gone through another bit of documentation about E language. Now about remote objects.

E is secure by default and that’s is great. Enough said.

The thing that makes it so secure it’s the core of his RPC mechanism. Every object is remotable (no need of mixin classes or awful scaffolding). What it takes to remote an object? Two lines of code:

[code lang="javascript"] def sr := makeSturdyRef.temp(your_object) def uri := introducer.sturdyToURI(sr) [/code]

Now you have an encrypted uri to share (securely, use PGP or something like that) with your peers to gain access to the remote object.

To the other side now you have to get the remote object and call the method you want. Again… very easily:

[code lang="javascript"] def remote := sr.getRcvr() def val := remote <- call_the_method_you_want() [/code]

val is a promise as I explained earlier

Great, isn’t it?

Here the full details of the examples: Introducing Remote Objects

Related posts

  • Project thoughts
  • E, episode eleven (The Dream)
  • E, episode six (I/O)
  • E, episode thirteen (Conclusions)
  • nevow pastebin, the final episode
  • Comments are closed.