Comments on: Pseudo-RESTful http://blog.medryx.org/2008/06/18/pseudo-restful/ Observations of a physician software developer. Wed, 08 Sep 2010 08:26:32 +0000 http://wordpress.org/?v=2.6 By: maulin http://blog.medryx.org/2008/06/18/pseudo-restful/#comment-9 maulin Thu, 19 Jun 2008 04:35:12 +0000 http://blog.medryx.org/?p=18#comment-9 Ugh. Yes. That is EXACTLY what I meant. I guess I didn't understand this as thoroughly as I had hoped. I have created a slightly different approach to this, but now seeing how JsonRestStore is setup, I don't know how much value add there is. We'll see. I plan on posting about it later tonight. thanks again for your input. -maulin Ugh. Yes. That is EXACTLY what I meant. I guess I didn’t understand this as thoroughly as I had hoped. I have created a slightly different approach to this, but now seeing how JsonRestStore is setup, I don’t know how much value add there is. We’ll see. I plan on posting about it later tonight.

thanks again for your input.

-maulin

]]> By: Kris Zyp http://blog.medryx.org/2008/06/18/pseudo-restful/#comment-8 Kris Zyp Thu, 19 Jun 2008 04:28:25 +0000 http://blog.medryx.org/?p=18#comment-8 Maulin, I am not exactly certain what you mean by entity-manager, are you referring to the mechanism for triggering lazy loads on property access and recording property changes? I am not sure how you would like JsonRestStore split up. Here is the current breakdown of modules: JsonRestStore - Dojo Data API adapter JsonRest - Tracks changes and fires Rest services Rest - Remote communication service provider dojox.json.ref - Referencing manager for lazy loading and other forms of referencing Perhaps JsonRest or JsonRestStore would roughly correspond to your "entity-manager", and the Rest service would correspond to your "persister", not sure. You can definitely plug your own custom Rest service into JsonRestStore. It looks like: myService = function(id){ ... get data ... } myService.put = function(content) { ... save data ...} myService.post = function(target,content) { .. create new object ...} myService['delete'] = function(target){ ... delete object ...} If you providing getters and setters is what you have in mind for an entity-manager, you can also define schemas for JsonRestStore that define the prototype to use for the objects in the store: mySchema = { prototype: { getFoo:function(){return this.foo}, setFoo:function(val){this.foo =val} } } myStore = new JsonRestStore({service:myService,schema:mySchema}); Maulin,
I am not exactly certain what you mean by entity-manager, are you referring to the mechanism for triggering lazy loads on property access and recording property changes? I am not sure how you would like JsonRestStore split up. Here is the current breakdown of modules:
JsonRestStore - Dojo Data API adapter
JsonRest - Tracks changes and fires Rest services
Rest - Remote communication service provider
dojox.json.ref - Referencing manager for lazy loading and other forms of referencing
Perhaps JsonRest or JsonRestStore would roughly correspond to your “entity-manager”, and the Rest service would correspond to your “persister”, not sure. You can definitely plug your own custom Rest service into JsonRestStore. It looks like:
myService = function(id){ … get data … }
myService.put = function(content) { … save data …}
myService.post = function(target,content) { .. create new object …}
myService['delete'] = function(target){ … delete object …}

If you providing getters and setters is what you have in mind for an entity-manager, you can also define schemas for JsonRestStore that define the prototype to use for the objects in the store:
mySchema = {
prototype: {
getFoo:function(){return this.foo},
setFoo:function(val){this.foo =val}
}
}
myStore = new JsonRestStore({service:myService,schema:mySchema});

]]> By: maulin http://blog.medryx.org/2008/06/18/pseudo-restful/#comment-7 maulin Wed, 18 Jun 2008 17:29:33 +0000 http://blog.medryx.org/?p=18#comment-7 great idea. thanks. I actually thought about this "hack" some more, and had a more general thought: The reason I like JsonRestStore is that it has a VERY nice entity-manager (for lack of a better term). Its not that I need or want REST (I have a simple working RPC server already working with get/save/delete methods). I think the JsonRestStore actually has mixed concerns -- on the one hand an entity-manager, and on the other a "persister". Perhaps we could think about how to split the two, and then make REST a pluggable persister into the entity-manager? great idea. thanks.

I actually thought about this “hack” some more, and had a more general thought: The reason I like JsonRestStore is that it has a VERY nice entity-manager (for lack of a better term). Its not that I need or want REST (I have a simple working RPC server already working with get/save/delete methods).

I think the JsonRestStore actually has mixed concerns — on the one hand an entity-manager, and on the other a “persister”. Perhaps we could think about how to split the two, and then make REST a pluggable persister into the entity-manager?

]]> By: Kris Zyp http://blog.medryx.org/2008/06/18/pseudo-restful/#comment-6 Kris Zyp Wed, 18 Jun 2008 15:56:10 +0000 http://blog.medryx.org/?p=18#comment-6 May I suggest something like this for REST blocking servers: var defaultXhr = dojo.xhr; dojo.xhr = function(method,args,hasBody){ if(method!="GET"){ args.url += (args.url.indexOf('?') > 0 ? "&" : "?" ) + "action=" + method.toLowerCase(); if(method=="PUT"){ args.postData = args.putData; } method = "POST"; } return defaultXhr(method,args,hasBody); } That way all your requests that use PUT, POST, and DELETE will automatically have the correct "action" parameter. I didn't test this, but I think it should work. May I suggest something like this for REST blocking servers:

var defaultXhr = dojo.xhr;
dojo.xhr = function(method,args,hasBody){
if(method!=”GET”){
args.url += (args.url.indexOf(’?') > 0 ? “&” : “?” ) + “action=” + method.toLowerCase();
if(method==”PUT”){
args.postData = args.putData;
}
method = “POST”;
}
return defaultXhr(method,args,hasBody);
}

That way all your requests that use PUT, POST, and DELETE will automatically have the correct “action” parameter. I didn’t test this, but I think it should work.

]]>