There is an issue when you use the MCWS SetInfo command to modify date tags on a file.
The syntax of the MCWS call is as follows (where "dddd" is supposed to be a date value encoded as a large integer)..
GET /MCWS/v1/File/SetInfo?File=123&Field=Date%20Created&value=dddd HTTP/1.1
Now there are some control points out there (even ones belonging the JRiver) that do not encode the date "dddd" as a large integer, but rather encode it as a plain text date, such as "6/12/2016" or "2016-06-12" etc. being the plain text date that the user types in. e.g. as follows..
GET /MCWS/v1/File/SetInfo?File=123&Field=Date%20Created&value=6/12/2016 HTTP/1.1
The syntax shown above fails. So my request is that you kindly extend the MC MCWS server SetInfo syntax to allow the existing encoding syntax, plus also an extended syntax allowing plain text date values as well. i.e. So that the MCWS server will parse and convert "6/12/2016" or "2016-06-12" or similar plain text date values, to MC internal date values.
Obviously you could insist that every control point must deliver the proper long integer date encoding, but I think it would provide much more value if you extended the SetInfo syntax on the MC MCWS server side. This makes it easier for external users to write add ons.
( Note that I posted a bug report recently in this forum but Henrik moved it over to Remotes, and we all know that over there, the bug will suffer a long and painful death by neglect. However if you extend the MCWS server syntax as requested, then that bug will be fixed without you having to touch JRemote.
http://yabb.jriver.com/interact/index.php/topic,106690.0.html )
Author
Topic: Problem with Date tagging syntax via MCWS SetInfo command (Read 3071 times)