Policies work?

0 views
Skip to first unread message

sega

unread,
May 29, 2010, 6:14:32 PM5/29/10
to FluidDB Discuss
Hello,

Every time I send a request about policies I get the message 404 -
Malformed policies request. I think I send the request according
FluidDB API. It is easy to reproduce with the following URL:
http://sandbox.fluidinfo.com/policies/gts_bcn/tag-values/update.

What is my error?

Thank you

Terry Jones

unread,
May 31, 2010, 5:33:19 PM5/31/10
to fluiddb...@googlegroups.com
Hi Sega

Actually, it's not your error, it's ours.

The documentation should not have mentioned an UPDATE action for
tag-values. There was a small change to remove the UPDATE action back in
January (see discussion here http://bit.ly/aaCWHV) and it looks like I
forgot to remove mention of UPDATE from the documentation at
http://doc.fluidinfo.com/fluidDB/permissions.html

That's now been corrected. Sorry for the inconvenience!

You'll notice that the conclusion of that discussion was that we should
probably use WRITE (not CREATE) as the action for writing a tag value. I
didn't make that change back in January, partly due to lack of time and
partly from wanting to minimize changes to the API. We still have an
unresolved (internal) ticket on that one, seeing as everyone agreed it
probably should become WRITE.

Terry

sega

unread,
Jun 1, 2010, 4:48:23 PM6/1/10
to FluidDB Discuss
Hi Terry,

> Actually, it's not your error, it's ours.
>
> The documentation should not have mentioned an UPDATE action for
> tag-values.  There was a small change to remove the UPDATE action back in
> January (see discussion herehttp://bit.ly/aaCWHV) and it looks like I
> forgot to remove mention of UPDATE from the documentation athttp://doc.fluidinfo.com/fluidDB/permissions.html

My tests work perfectly now. Thank you.

> That's now been corrected.  Sorry for the inconvenience!

Don't worry. Errare humanun est.

> You'll notice that the conclusion of that discussion was that we should
> probably use WRITE (not CREATE) as the action for writing a tag value. I
> didn't make that change back in January, partly due to lack of time and
> partly from wanting to minimize changes to the API. We still have an
> unresolved (internal) ticket on that one, seeing as everyone agreed it
> probably should become WRITE.

Yes, it seems more logic.

Thank for your answer
Reply all
Reply to author
Forward
0 new messages