thank you for your reply.
yes the blur plugin api doesn’t return the filename but contrary to the base api /osc/commands/execute it doesn’t return the id either
e.g.
{
"id": "133",
"name": "camera.takePicture",
"progress":{
"completion": 0
},
"state": "inProgress"
}
without the id I cannot query the api to find out when the picture is ready and get the file URL like you would normally do using the base osc api
e.g.
POST /osc/commands/status
request
{
"id" : "133"
}
response
{
"name": "camera.takePicture",
"results":{
"fileUrl": "http://192.168.1.163/files/150100525831424d4207c503deb28400/100RICOH/R0010163.JPG"
},
"state": "done"
}
The plugin actually calls this same api when taking pictures but it doesn’t expose it on the web interface, instead binds the results to an httplistener which I don’t know whose purpose is.
My feeling is that the face blur plugin api workflow is not complete as it doesn’t allow to access the produced images, instead after taking the picture one has to use the ricoh app to download them.
Using a mix of face blur plugin api and base osc api from the faceblur webclient is also out of the question because of issues with CORS as the api are on different ports.
The only solution I understand is to extend by enhancing or exposing part of the osc api into the face blur api, which is what I am doing at the moment.
cheers
Massimo