Patch new javascript api lib based on EEEE Open Resty database services to DOJO

[guest]

This is Carrie Zhang. I have sent a CLA to your cla group, and now want to submit my patch to DOJO.

I have wrote a introduction of this API file, please have a look at it, ​http://www.carriezh.cn/carrie/2008/03/dojo-openapi-js-1.html

The Javascript file is in ​http://www.carriezh.cn/openapi.js

Thanks, Carrie Zhang (carrie.zhxj@…) 03/12/2008

[Adam Peller]

Hi Carrie. Thanks for your patch.

I'm not at all familiar with EEEE or open resty. I'm not sure who would be best suited to evaluate this or the need for inclusion in dojox. Would it make sense to integrate this as a dojox.data service? Or would it be best served if maintained separately by the maintainer and referenced as a dojo community project?

[guest]

Hi, I think it is suitable to be contained in dojox/data.

The EEEEOpenResty is an resty api based on free database cluster, and it provides the services to store any kinds and formats of data, (looks like google-base a little bit), and the following link is the introduction of this service platform: ​http://search.cpan.org/~agent/OpenResty-0.1.0/lib/OpenResty/Spec/REST.pod

The EEEEOpenResty platform will be used widely, for it supports any kinds of language to send request to, through the HTTP spec (POST, GET, PUT, DELETE). What I have written is just javascript api. I want to help the users who used that free database service through js and DOJO.

Thanks a lot,
Carrie Zhang

[Adam Peller]

in order to be a part of the dojox.data subproject, it would need to implement the dojo.data API.

[guest]

I think it focuses on cross-domain POST & GET info. And I have only used dojo.io.*, should it be placed to dojox.io ?

[guest]

In fact, the datastore format and schema which save in EEEEopenResty server are not uniform. They can be defined by the creator of any single application . So is it fit for using dojo.data? or only use dojo.io features directly?

Hope your reply
Thanks,
Carrie Zhang
03/12/2008

[Tom Trenka]

Reviewed this with Kris Zyp (reassigning to him); both of us feel that this is kind of basic in its current form.

What I think we'd like to see instead is an SMD file for this; Kris will help you get started in that direction...

[kriszyp]

Carrie, In the interest of consistency of Dojo services, I would recommend that Dojo support for EEEE Open Resty be approached two-fold:

1. If possible, I would like to see the Open Resty API described with an SMD (​http://groups.google.com/group/json-schema/web/service-mapping-description-proposal). With an SMD, no code would be required, the SMD could simply plug into the dojox.rpc.Service module and auto-generate the service endpoints, and users could use a standard Dojo service API to communicate with Open Resty. If you could create an SMD, that would be great, we are definitely interesting amassing more SMD definitions.
2. I have created dojo.data implementation for REST services called JsonRestStore? (​http://trac.dojotoolkit.org/ticket/5987, it is not committed yet, feel free to ask for that). If you are properly following REST semantics, I think there is a good chance this data store could work with your server's HTTP API (especially in combination with an SMD). Having dojo.data store could be very beneficial, since it can plugin to various widgets. JsonRestStore? already works with a several REST servers out there, and it would be great to add another with Open Resty.

Anyway, I would be glad to help if you have any questions about getting these working.

[Kris Zyp]

I haven't seen anything contributed as far as an SMD, so I am assuming it won't happen. Dojo already has support for a REST interface per the HTTP specification RFC 2616 with the JsonRestStore?, so I don't think we need any additional modules.