axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2C-270) base64 encoding/decoding should be implemented as a stream
Date Thu, 24 Apr 2008 12:29:21 GMT


Samisa Abeysinghe resolved AXIS2C-270.

    Resolution: Won't Fix

We are kind of trying to address the streaming issues with MTOM caching model. However it
is not the same as proposed by this issue. 
This proposal should be revisited for 2.x family.

> base64 encoding/decoding should be implemented as a stream
> ----------------------------------------------------------
>                 Key: AXIS2C-270
>                 URL:
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: Current (Nightly)
>            Reporter: James Clark
>            Priority: Minor
> You should have something like this
> axis2_output_stream_t *axis2_create_base64_output_stream(axis2_output_stream_t *, const
axis2_env_t *);
> Let's call the argument stream s1 and the returned stream s1. When you write bytes on
s2, they will be written out as base64 encoded bytes on s2.  
> Similarly, mapping base64 to binary is an input_stream.
> This allows you to efficiently deal with encoding/decoding large quantities of base64
> You can have your existing functions as well.  They should both be implemented on top
of a lower-level layer that copies from buffer to buffer without doing allocation, e.g. something
> base64_decode(const char *from, size_t from_length, char *to, size_t to_length, size_t
*n_read, size_t *n_written)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message