On 11/06/2012 07:53 PM, Junchang(Jason) Wang wrote:
On Tue, Nov 6, 2012 at 4:47 PM, Vijay K. Gurbani <[email protected]
<mailto:[email protected]>> wrote:
2) Use multi-part MIME. One part is the normal
"application/alto-error+json" and the other part could be
"text/plain" that describes the error in more detail.
We can try to implement this in our ALTO server. But whether it's better
to mention that in some documents so that clients can follow? In other
words, clients should be aware of error description part. Is that right?
Yes, at least aware enough that they decode the multipart MIME and
render the "text/plain" for human consumption. But even if they do
not, the problem is apparent when one uses a packet sniffer (tcpdump,
wireshark, etc.) to look at the traffic.
From the ease of use perspective, using the Reason-Phrase is probably
the way to go.
We could probably have an "Implementer's Guide" section in draft-
gurbani-alto-interop-cases where we provide relevant information.
Probably best to put it there instead of the protocol document.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / [email protected]
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
