🚀 go-pugleaf

fortunat@interpath.com (Jumpstile Turner) wrote:

>   Incidently, I changed (and have been changing) a lot of stuff over 
>to Win32 API calls, memory and file handling.  It sure seems a lot 
>faster now as opposed to using the standard C stuff, but this might be 
>my imagination.  

The right way to do this is to write your own source and destination
drivers. I wrote a pair to read and write from/to MFC CArchives, and
used this to integrate it into a JPEGImage class that I plugged into
the Image clases from Barkakati's _Visual C++ Developer's Guide_.

This is a pretty slick way to go - I can just JPEGimage->serialize()
onto a TCP connection! Using the MFC 4.0 CSocket class, it only takes
a couple of lines of code to open a CSocket, open a CArchive onto the
CSocket, and then serialize the image. Poof! It shows up on my little
Perl server at the other end. (And will start showing up on my web
site, once I write the buffering code into the Perl program and the
NSAPI function to read it from the memory buffers...) 
________________________________________________________________________
jtara@live.net  A new video clip (Netscape 1.1+) of San Diego Bay every half hour:
 <URL:http://live.net/sandiego/> Rated top 5% & "best 1000" by Point Communications
jtara@mediashare.com Tools and services for CD-ROM and online catalogs:
 <URL:http://www.mediashare.com/> Also rated top 5% by Point Communications