I think you’re confusing SMD with REST.
SMD supports multiple envelopes (including REST, but not only !)

As you can see in the SMD file:
http://javascript.neyric.com/wireit/backend/php/WiringEditor.smd ,
the WiringEditor examples uses JSON-RPC, where all remote method calls use POST request.

Sadly, YUI-rpc (the module that the WiringEditor uses) doesn’t support REST yet…

Thanks for your cheering !

WiringEditor.getValue() and Layer.getWiring() are indeed very similar methods, but they are used at a different modelisation level.

In the WiringEditor, a language definition is created (list of module definitions). The value of the created graph is returned using this modules.

In the layer, there is no such definition. The getWiring value only returns the Container instances definition.

If you use the WiringEditor, WiringEditor.getValue() will return the entire wiring setup, and you usually don’t need to use Layer.getWiring()

The SMD allows you to choose a HTTP verb for use with each method – as it is, the example chooses POST to do a load, a listing, a save and a delete, which seems a poor use of HTTP.

J.

I think the WiringEditor is pretty darn cool. I’ve been looking through the source to understand how this works, and I’m confused by something – the WiringEditor.getValue() method and the Layer.getWiring() method seem to be intended to do similar things, although they return objects that are different in structure – indeed, getWiring() doesn’t seem to include the ‘value’ of the container at all, just its config. Why not combine these two functions into a standard that returns a JSON description of the entire wiring setup?

J.