- From: Vogel Peter (FV/SLM) * <Peter.Vogel2@de.bosch.com>
- Date: Tue, 4 Dec 2001 16:01:03 +0100
- To: www-mobile@w3.org
Hello Alan, > Von: Alan Ng [mailto:ngyahloon@yahoo.com] > > digest fixed? Any place where i can get the Base64 > coding in C/C++? Perhaps a Java implementation helps as well. You will find one within the Jigsaw Server from W3C. > When we encode the CC/PP > descriptions, do we need to include "\n" or is > everything in a long sequence? It is my understanding that you have to omit all CR, LF within the CC/PP description, following the Profile-Diff header (see. 5.2.2 in CCPPex). When you transmit CR,LF in your CC/PP description e.g. in Jigsaw, it will not work (at least, when you have a CRLF in the first line of your description, starting with Profile-Diff-1:). > 2. When we append the complete profile, at which part > should we put in the CR/LF? > > For example: > > GET /example.htm HTTP/1.1 (CR/LF) > Opt: "http://www.w3.org/1999/06/24-CCPPexchange"; > ns=19 (should we put CRLF here?) Yes. Seems to work. > 19-Profile: "http://www.abc.com/default", > "1-sldknaevsxlskngaedqadf==" (should we put CRLF > here?) Yes. Seems to work. > Lastly, for the profile diff header value, should CRLF > be appended at the end (after </RDF>) or after each > line? I think it should be appended at the end only. Jigsaw filters some CRLF within the CC/PP description. But it has problems with a CRLF in the first line of the Profile-Diff header. Regards, Peter Vogel.
Received on Tuesday, 4 December 2001 11:24:36 UTC