Skip to search.
soapbuilders

Group Information

  • Members: 1198
  • Category: Protocols
  • Founded: Jan 27, 2001
  • Language: English
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Message search is now enhanced, find messages faster. Take it for a spin.

Messages

  Messages Help
Advanced
echoBase64   Message List  
Reply Message #2494 of 10830 |
Re: [soapbuilders] echoBase64

If one is using the datatypes defined by XML Schemas March 30, 2001, then
the rules of those datatypes apply, not the commentary in the SOAP
specification which was describing earlier and unfinished schema types. The
XML Schemas specification description of base64Binary refers to RFC 2045,
which in turn says


Table 1: The Base64 Alphabet

Value Encoding Value Encoding Value Encoding Value Encoding
0 A 17 R 34 i 51 z
1 B 18 S 35 j 52 0
2 C 19 T 36 k 53 1
3 D 20 U 37 l 54 2
4 E 21 V 38 m 55 3
5 F 22 W 39 n 56 4
6 G 23 X 40 o 57 5
7 H 24 Y 41 p 58 6
8 I 25 Z 42 q 59 7
9 J 26 a 43 r 60 8
10 K 27 b 44 s 61 9
11 L 28 c 45 t 62 +
12 M 29 d 46 u 63 /
13 N 30 e 47 v
14 O 31 f 48 w (pad) =
15 P 32 g 49 x
16 Q 33 h 50 y

The encoded output stream must be represented in lines of no more
than 76 characters each. All line breaks or other characters not
found in Table 1 must be ignored by decoding software.

See http://www.ietf.org/rfc/rfc2045.txt, section 6.8.

It is pretty clear that white space and any other non-table-1 character
should be ignored during parsing.

What I am not sure of, since RFC 2045 was written in the context of MIME
representation, is whether the 76-character restriction applies to
xsd:base64Binary. I've copied the editors of the schema specification for
clarification.

----- Original Message -----
From: "Rich Salz" <rsalz@...>
To: <soapbuilders@yahoogroups.com>
Sent: Thursday, April 26, 2001 6:48 PM
Subject: Re: [soapbuilders] echoBase64


> I took the sentence "However, the line length restrictions that normally
> apply to base64 data in MIME do not apply in SOAP" to mean that when
> serializing out base64 you don't have to worry about wrapping, and so it
> should be one long string. but i can see how that might not be the
meaning.

I took it to read "you MAY send one long line, but it is not a MUST that
you do so."

I'd recommend that at least linebreaks be ignored, probably
linebreak-whitespace is best, but ignoring all whitespace is okay.
/r$

To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/







Fri Apr 27, 2001 2:58 am

yahoo@...
Send Email Send Email

Message #2494 of 10830 |
Expand Messages Author Sort by Date

I've been trying out echoBase64 (type SOAP-ENC:base64) with a few implementations and have run across a couple problems. The base64 string I am sending...
David Crowley
dcrowley@... Send Email
Apr 26, 2001
8:57 pm

I took the sentence "However, the line length restrictions that normally apply to base64 data in MIME do not apply in SOAP" to mean that when serializing out...
Simon Fell
sfell@... Send Email
Apr 26, 2001
9:02 pm

Hi, David! I don't believe it's valid. While it might be properly decoded in MIME message, in my opinion any whitespace inside this element should be avoided. ...
Paul Kulchenko
paulclinger@... Send Email
Apr 26, 2001
9:08 pm

... The WSDL says whitespace="collapse" is fixed, so leading and trailing whitespace should be OK. It would be nice if internal whitespace was OK too, as there...
blm@... Send Email Apr 26, 2001
9:16 pm

Well, the example in section 5.2.3 shows at least leading and trailing whitespace... I don't see a reason to specifically disallow whitespace. I would think...
David Crowley
dcrowley@... Send Email
Apr 26, 2001
9:17 pm

+1 here. -Jake...
Jake Savin
jake@... Send Email
Apr 26, 2001
9:20 pm

I think trailing and leading whitespace is ok, but not in the middle ... From: David Crowley [mailto:dcrowley@...] Sent: Thursday, April 26, 2001 2:18...
Simon Fell
sfell@... Send Email
Apr 26, 2001
9:20 pm

I did some digging. Quote from the XML schema on whitespace collapse: replace All occurrences of #x9 (tab), #xA (line feed) and #xD (carriage return) are ...
David Crowley
dcrowley@... Send Email
Apr 26, 2001
10:58 pm

Hi, David! Agree. SOAP::Lite ignores whitespaces in base64 encoded elements. I've also added support for sparse arrays (in my understanding ALL elements should...
Paul Kulchenko
paulclinger@... Send Email
Apr 27, 2001
4:46 am

... I took it to read "you MAY send one long line, but it is not a MUST that you do so." I'd recommend that at least linebreaks be ignored, probably ...
Rich Salz
rsalz@... Send Email
Apr 27, 2001
1:43 am

If one is using the datatypes defined by XML Schemas March 30, 2001, then the rules of those datatypes apply, not the commentary in the SOAP specification...
Andrew Layman
yahoo@... Send Email
Apr 27, 2001
3:02 am

RFC 2045 says that, on generation, the base64 output stream must have a line break every 76 or fewer characters. It also says that, on input, line break and...
Andrew Layman
andrewl@... Send Email
Apr 30, 2001
5:28 pm

... I would say yes, as it just says it's based on RFC 2045. However, I would say that any server that checks that was being overly pedantic. Brian...
blm@... Send Email Apr 30, 2001
5:51 pm
Advanced

Copyright © 2010 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines NEW - Help