I'm new to Smartclient and so far I love it. The only problem is that I use .net on the back end. With other libraries, I've been using a library called Jayrock to Javascript RPC calls (http://jayrock.berlios.de/). All that is required is that special request headers be added:
'X-JSON-RPC' = 'MethodToUseOnServer'
and 'Content-type' = 'text/plain; charset=utf-8'
All responses are of a set format following the RFCs for RPC calls and the library (de)serializes to/from json.
With minor modifications, I could probably get smartclient to use services using jayrock on the backend. Is there any documentation as to the actual formats of calls to the server and returned data formats? Otherwise, I could probably look through the Java code (if available) and come up with an equivalent in c# or vb.net and modify the Jayrock library to work. Otherwise, I would just need a map of how the calls are put together (request headers, method name location in the request, (de)serialize formats, etc).
For example: For paging (live grid binding), the requests must have some standard format:
offset=200&per_page=50&data=fooBar
the request header something like:
RPC-METHOD = 'livegrid1pager'
of course, if the method requires more data, it may use the POST method, etc...
Please let me know if Isomorphic would like the code when I have it working. It may be an easy way to provide .net support for Smartclient data binding.
Thanks,
Paul Perrick
'X-JSON-RPC' = 'MethodToUseOnServer'
and 'Content-type' = 'text/plain; charset=utf-8'
All responses are of a set format following the RFCs for RPC calls and the library (de)serializes to/from json.
With minor modifications, I could probably get smartclient to use services using jayrock on the backend. Is there any documentation as to the actual formats of calls to the server and returned data formats? Otherwise, I could probably look through the Java code (if available) and come up with an equivalent in c# or vb.net and modify the Jayrock library to work. Otherwise, I would just need a map of how the calls are put together (request headers, method name location in the request, (de)serialize formats, etc).
For example: For paging (live grid binding), the requests must have some standard format:
offset=200&per_page=50&data=fooBar
the request header something like:
RPC-METHOD = 'livegrid1pager'
of course, if the method requires more data, it may use the POST method, etc...
Please let me know if Isomorphic would like the code when I have it working. It may be an easy way to provide .net support for Smartclient data binding.
Thanks,
Paul Perrick
Comment