Dojr.NET Dojo RPC Library

Updated Release: March 2008 Edition (Apr 06, 2008)

Thu, 31 Jul 2008 04:35:18 GMT

This is the original release of Dojr.NET for .NET 2.0.

NEW POST: More WCF based implementation of JSON-RPC

zestbot — Fri, 25 Apr 2008 03:59:41 GMT

Well for the public record, I'll continue this thread...
Instead of creating a custom binding to map the content type application/json-rpc to Json it is possible to set the content type on the dojo rpc service.
eg
var svc = new dojo.rpc.JsonService('myservicesvc/ajaxEndpoint/?smd');
svc.contentType = "application/json";

now WCF will encode the message body as json and it can be retrieved using
DojoMessage rpcMessage = message.GetBody<DojoMessage>(new DataContractJsonSerializer(typeof(DojoMessage)));

Arguably not the best way, but the simplest way get things going. It would be nice if application/json-rpc was one of the default mappings in wcf.

NEW POST: More WCF based implementation of JSON-RPC

zestbot — Thu, 24 Apr 2008 04:30:13 GMT

OK, Ill undo the glory earned by the getting the "first post" by replying to myself :-(

The answer to my question is that WCF and WebHttpBehavior can be used as described above. The trick is getting the json out of the json-rpc request message at the operation selection time.

Quoting from this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2790925&SiteID=1

"Endpoints with the WebHttpBinding (or custom bindings with the WebMessageEncodingBindingElement) have a "content type mapper" that will tell WCF what is the format of the request, based on the content-type of the request (the three formats supported in .NET FX 3.5 are Xml, Json and Raw). In the case of all operations in the endpoint with exclusively Stream parameters, the WebServiceHost will map all requests to the "Raw" mode. If there is at least one operation that has a parameter other than Stream, then this mapping won't be added, and the default mapping kicks in (application/json and text/json to Json; application/xml, text/xml and some others to Xml; everything else to Raw)."

So the json comes through on the message as binary within an xml element eg <binary>binaryencodedjson</binary>

therefore it can be accessed as follows
XmlDictionaryReader reader = message.GetReaderAtBodyContents();
byte[] bytes = reader.ReadElementContentAsBase64();
string myJason = Encoding.UTF8.GetString(bytes);

This proves how it is working but, it would be better extend the "content-type-mapper" to map application/json-rpc to Json as well then I guess it could be retrieved using something like

DojoMessage rpcMessage = message.GetBody<DojoMessage>(new DataContractJsonSerializer(typeof(DojoMessage)));

Carey

NEW POST: More WCF based implementation of JSON-RPC

zestbot — Thu, 24 Apr 2008 00:35:33 GMT

Hi,
Great propject. I am trying to do the same thing but using more of WCF.

I am finding implementing the operation selector for json-rpc difficult in WCF, and see that you chose to use old httphandler stuff rather than the new webHttpBinding stuff. Is there a good reason for that?

I have tried to implement pretty much the same as you have but using WebHttpBehavior and extending WebHttpDispatchOperationSelector to override SelectOperation. My problem is not being able to figure out how to get the json out of the message at the operation selection stage.

Any thoughts on the pros and cons of using webHttpBinding over httphandler and suggestions on getting the json out of the message in SelectOperation would be appreciated.

Cheers

Carey

UPDATED RELEASE: March 2008 Edition (Apr 06, 2008)

Wed, 09 Apr 2008 16:22:46 GMT

*This is the current revision of Dojr.NET and is therefore not archived into ZIP. Get the source code for this revision.*

This is the original release of Dojr.NET for .NET 2.0.

Given the nature of open source projects, ZIP are normally obsolete as soon as they are published and therefore, they are only used for archived projects. Because of this, +you should always get the latest code from the source code section+. ZIP downloads are for archived revisions only.

UPDATED RELEASE: March 2008 Edition (Apr 06, 2008)

Wed, 09 Apr 2008 16:22:01 GMT

*This is the current revision of ESV Bible Web Service 2.0 Framework and is therefore not archived into ZIP. Get the source code for this revision.*

This is the original release of Dojr.NET for .NET 2.0.

Given the nature of open source projects, ZIP are normally obsolete as soon as they are published and therefore, they are only used for archived projects. Because of this, +you should always get the latest code from the source code section+. ZIP downloads are for archived revisions only.

UPDATED RELEASE: March 2008 Edition (Apr 06, 2008)

Wed, 09 Apr 2008 04:34:20 GMT

*This is the current revision of Squid and is therefore not archived into ZIP. Get the source code for this revision.*

This is the original release of Dojr.NET for .NET 2.0.

Given the nature of open source projects, ZIP are normally obsolete as soon as they are published and therefore, they are only used for archived projects. Because of this, +you should always get the latest code from the source code section+. ZIP downloads are for archived revisions only.

UPDATED RELEASE: March 2008 Edition (Apr 06, 2008)

Wed, 09 Apr 2008 01:15:30 GMT

This is the original release of Dojr.NET.

Given the nature of open source projects, ZIP are normally obsolete as soon as they are published and therefore, they are only used for archived projects. Because of this, +you should always get the latest code from the source code section+. ZIP downloads are for archived revisions only.

UPDATED RELEASE: Original CodePlex Release (Apr 06, 2008)

Wed, 09 Apr 2008 01:13:43 GMT

This project has been previously hosted else where and has been transferred to CodePlex.

Given the nature of open source projects, ZIP are normally obsolete as soon as they are published and therefore, they are only used for archived projects. Because of this, +you should always get the latest code from the source code section+. ZIP downloads are for archived revisions only.

UPDATED RELEASE: Original CodePlex Release (Apr 06, 2008)

Wed, 09 Apr 2008 00:41:06 GMT

This project has been previously hosted else where and has been transferred to CodePlex.

The source code will always be in the source code section. "ZIP" downloads are normally obsolete as soon as they are published.

UPDATED RELEASE: Original CodePlex Release (Apr 06, 2008)

Wed, 09 Apr 2008 00:39:50 GMT

This project has been previously hosted else where and has been transferred to CodePlex.

This is CodePlex: get the code. ZIPs are redundant.

UPDATED WIKI: Home

quantum00 — Tue, 08 Apr 2008 05:25:36 GMT

Project Description
Dojr.NET is a simple framework created to allow easy creation of dojo.rpc services by defining a class which inherits from a specific base class, adding one or more attributes, and registering it as an HttpHandler.

NetFXHarmonics Blog

Dojr.NET Announcement and Overview
http://www.netfxharmonics.com/2008/01/DojrNET-Dojo-RPC-Library-NET-20

As a Training Tool

Dojr.NET is built on .NET 3.5 technology and attempts to give WCF-like usability. Dojr.NET actually internally uses DataContractJsonSerializer which WCF 3.5 internally uses for its own JSON serialization. Dojr.NET, like WCF, uses attributes to declare specific service operations. However, unlike WCF, Dojr.NET inherits from a class, like COM+, where as it is idiomatic in WCF to implement a service contract interface. Dojr.NET creates each service as an HttpHandler which is then registered to ASP.NET at a particular endpoint.

UPDATED WIKI: Home

quantum00 — Tue, 08 Apr 2008 05:23:01 GMT

NetFXHarmonics Blog

Dojr.NET Announcement and Overview
http://www.netfxharmonics.com/2008/01/DojrNET-Dojo-RPC-Library-NET-20

As a Training Tool

Dojr.NET is a NetFXHarmonics product built on .NET 3.5 technology and attempts to give WCF-like usability. Dojr.NET actually internally uses DataContractJsonSerializer which WCF 3.5 internally uses for its own JSON serialization. Dojr.NET, like WCF, uses attributes to declare specific service operations. However, unlike WCF, Dojr.NET inherits from a class, like COM+, where as it is idiomatic in WCF to implement a service contract interface. Dojr.NET creates each service as an HttpHandler which is then registered to ASP.NET at a particular endpoint.

Source code checked in

quantum00 — Sun, 06 Apr 2008 19:01:05 GMT

Source code checked in

quantum00 — Sun, 06 Apr 2008 18:58:33 GMT

Source code checked in

quantum00 — Sun, 06 Apr 2008 18:56:52 GMT

Source code checked in

quantum00 — Sun, 06 Apr 2008 18:53:18 GMT

CREATED RELEASE: Original CodePlex Release (Apr 06, 2008)

Sun, 06 Apr 2008 14:36:18 GMT

This project has been previously hosted else where and has been transferred to CodePlex.

UPDATED WIKI: Home

quantum00 — Sun, 06 Apr 2008 06:05:42 GMT

Project Description
Dojr.NET is a simple code created to allow easy creation of dojo.rpc services that are usable is a manner idiomatic for ASP.NET.

NetFXHarmonics Blog

Dojr.NET Announcement and Overview
http://www.netfxharmonics.com/2008/01/DojrNET-Dojo-RPC-Library-NET-20

As a Training Tool

Source code checked in

quantum00 — Sun, 06 Apr 2008 06:00:48 GMT