Re: Can the HTTPAPI service program be trimmed down to a smaller size?

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi James,

Based on your desire to have something very small, and your rather small 
requirements, I wonder if you wouldn't be better off writing your own 
simple GET tool?

There are examples of this in my socket tutorial:
http://www.scottklement.com/rpg/socktut/firstclient.html

It certainly doesn't have anywhere near the features or robustness of 
HTTPAPI -- but it sounds like you don't really want them.


James Lampert wrote:
> John Rusling wrote:
>> I can see why a person might want to do that, and I haven't looked at
>> that code in awhile but as I recall, a lot of the pieces are intricately
>> woven together, ie procedures using other procedures, etc.
> 
> Yes, I looked it over this morning, and filled a sheet of scratch paper 
> with dependencies. Also found that the biggest single module, containing 
> everything I'm calling, and most of what it's calling, also contains 
> most of what I'd be inclined to jettison.
> 
>> I'd leave it intact and just use what you need, your gains are, 1) it's 
>> all in place for the next unforeseen request. 2) upgrading it if new
>> functionality is ever included with a newer version.
> 
> Oh, well, it was an idea. I guess I can simply yank observability. That 
> shrinks it down a bit. Or maybe I could stub-out the unused top-level calls.
> 

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------