[jira] Commented: (XERCESC-1247) Base64::decode fails when string contains consecutive whitespace

[xe...@xml.apache.org]

The following comment has been added to this issue:

     Author: David Bertoni
    Created: Fri, 30 Jul 2004 2:16 PM
       Body:
Unfortunately, XML schema has more stringent requirements:

http://www.w3.org/2001/05/xmlschema-errata#Errata2

See E2-54 for more details.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XERCESC-1247?page=comments#action_36962

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1247

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1247
    Summary: Base64::decode fails when string contains consecutive whitespace
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Utilities
   Versions:
             2.5.0

   Assignee: 
   Reporter: Frank Pilhofer

    Created: Fri, 30 Jul 2004 11:57 AM
    Updated: Fri, 30 Jul 2004 2:16 PM
Environment: N/A

Description:
The Base64::decode function requires that the input string does not
contain more than one consecutive whitespace.

However, there is no such restriction in RFC 2045, "Multipurpose
Internet Mail Extensions," which defines the Base 64 encoding in
section 6.8. In fact, it clearly states that

 Any characters outside of the base64 alphabet are to be ignored in
 base64-encoded data.

Note that the current implementation would, e.g., fail if the
input string contains a CR LF sequence.

Proposed resolution: get rid of the "inWhiteSpace" test.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

Re: XMLString::transcode performance

[Vitaly Prapirny <ma...@mebius.net>]

Markus wrote:
> but shouldn't
> it still be equally fast every time?
No. AFAIR, you have no any guarantee for code execution time in
multitasking non-realtime operating system.

Good luck !


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

XMLString::transcode performance

[Markus <ma...@mail.student.oulu.fi>]

Now that I've succesfully upgraded to 2.5.0 
I am looking for ways to speed up my app.

Consider the following code bit.

while(repeat a few thousand times)
{
    XMLCh* ch1 = XMLString::transcode("Name");
    
    // do something...

    delete []ch1;

    // with this the performance is approx. the same too...
    //XMLString::release(&ch1);
}

With ~12 000 repeats in that while loop the line times for
transcode call are: (units unknown, but they are comparable)
Shortest: 18,401
Average: 41,968
Longest: 4,951,682

Now I know that it is not necessary to make that
call with constant arguments repeatedly, but shouldn't
it still be equally fast every time?

Markus

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org