I have some thoughts about application/vnd.oma.pres-content+xml.
I think that it should be the opportunity to GET/PUT pres-content. For now
only PUT operation is available, and during GET operation you can only get
the image content but not its meta-data.
I suggest the following:
If during GET operation I specify in the HTTP header
application/vnd.oma.pres-content+xml you can return the xml, if not - return
the image content. This compromise will allow you to support for almost 100%
the specification and for us to use it correctly.
What do you think about it?
2010/6/30 Saúl Ibarra Corretgé <firstname.lastname@example.org>
On 30/06/10 11:21, Grigorii Balutsel wrote:
Do you need some additional help to resolve these issue?
I've had no time to check this yet, sorry :-S I'll come back to you on that
when I find the time to fix it.
The second issue that I've found is about pres-content
(in the end of the document you can find examples)
GET method should return Content-Type:
application/vnd.oma.pres-content+xml, your server returns it, but the
content of it is not xml - it is image (PNG, GIF and so on).
It is an issue or I've missed something?
Yeah... actually we did that in purpose: the idea is to store the icon
through XCAP with a randomly generated name, so that it's sort of 'private'.
Then this can be advertised with CIPID (RFC 4482) and the user which sees
this URL in the icon field doesn't really know it was stored in XCAP so it
would expect to fetch the icon with a regular GET request.
We know it doesn't comply with the standard 100%, but it feels better this
way and yet nobody bothered implementing it that I'm aware (I'm actually
glad you do). Our test scripts (sipsimple project) work this way, maybe you
can test with them.
If this causes trouble in the future we shall change it.
Saúl Ibarra Corretgé