Re: [Animl-develop] Array Sizing for Base64 values

[Burkhard S. <b_...@us...>]

Dave,

thanks for the URL. I read through the specification. It looks like XOP 
can be applied to any existing XML document. It works by packaging the 
XML document into a multipart MIME container and extracting parts of the 
document. These extracted parts are moved to a new MIME part (which is 
8-bit clean) and is then referenced from the location is previously held 
in the document.

All this generates pretty significant overhead, mainly due to the MIME 
container and MIME boundaries, but also due to the reference pointers. 
So it only makes sense if large chunks of data are used.

AnIML is compatible with this specification. Very large (!) 
Base64-encoded data sets could be treated that way. There is nothing to 
keep users from applying it to their AnIML files. It's just that the XML 
parser reading the file later needs to support it. Since the tool 
support is extremely limited right now, we should wait and see if it 
catches on.

Best regards,
Burkhard


David Martinsen wrote:
> I just ran across this release of the "XML-binary Optimized Packaging" as a
> W3C recommendation: http://www.w3.org/TR/2005/REC-xop10-20050125. It strikes
> me that this has the potential to a) reduce the file size of AnIML files;
> and b) remove the need for encoding/decoding base64 strings, thereby
> improving performance of software processing AnIML files.
> 
> I'm not proposing a switch to this specification at this point, but just
> wanted to ask my learned colleagues whether this spec might make sense at
> some point in the future?
> 
> Regards,
> Dave
> 
> -----Original Message-----
> From: Burkhard Schaefer [mailto:b_...@us...] 
> Sent: Wednesday, December 15, 2004 9:51 PM
> To: AnIML Developer List
> Subject: [Animl-develop] Array Sizing for Base64 values
> 
> Regarding Mark B.'s question about Base64 array lengths: I think most 
> algorithms work the same way as the one you've written. You can infer 
> the number of values by looking at the length of the base64 string. (if 
> you know whether it contains float64 or float32 values)
> 
> This way you can find out how much memory you need to allocate before 
> actually decoding the base64 string.
> 
> Best wishes,
> Burkhard
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Animl-develop mailing list
> Ani...@li...
> https://lists.sourceforge.net/lists/listinfo/animl-develop
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Animl-develop mailing list
> Ani...@li...
> https://lists.sourceforge.net/lists/listinfo/animl-develop
>