Am 19.05.2012 22:26, schrieb Pragmatix:
Am 19.05.2012 22:18, schrieb Sönke Ludwig:
Am 19.05.2012 17:38, schrieb Pragmatix:
Hi,
first of all : GREAT WORK!What I need is JSONRest support following RFC 2616.
( http://www.ietf.org/rfc/rfc2616.txt )I would like to use vibe.d as REST Server back-end in conjunction with
dojo/dijit (front-end) to implement RIAs.This means that certain things should work as follows.
I have some additions planned for the current generator, which is still
very simple, but I'm not yet 100% sure about them.http://vibed.org/api/vibe.http.rest#registerRestInterface
Unfortunately, right now, my schedule is extremely tight. I will look
closer into your list of features once there some more time again -
range and query definitely sound like good additions.Danke Sönke , fair enough.
means for me that I can start working on the QR-code encoder/decoder.
btw. in case that you can spend a few minutes.. have a look at the zeal
REST implementation.
I had some time to make some first extensions. You can now have a method
'index' that acts as a "GET /" on the base folder specified and If the
first parameter is named 'id', it is translated as a directory name
(e.g. getName(id) -> GET /:id/name).
The "Range: ..." stuff needs some more thought on how to fit it nicely
into the API. An alternative would be to make an explicit JsonRestStore
implementation, because the scope of the registerRestInterface() is a
bit more general, but that would be something for someone else because I
would neither be able to properly test it nor would I use it.
I've looked at zeal.d before and I like it and would also consider it
for new apps. However, the goal of the http.rest stuff is more to have a
seemless D-to-D RPC facility.
Btw. one other aspect to think about would be how to best integrate
authroization checks.