Re: httpapi.XML parse problem

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Mike,

Mike Krebs wrote:
> Is it possible to take the "local" version command one step higher
> and do something like:
> 
> Version('project')


It's not clear to me what 'project' would be?  Is it the name of a 
service program?  Or the marketed name of a product/project?  If the 
latter, how would the routine know which service program to dynamically 
bind to?

> For HTTPAPI, it would look like this: version('HTTPAPI') and would return
> string value 1.23.

But... it would have to somehow know to bind to HTTPAPIR4 and call a 
routine named 'version'...   not sure that I like that.  How would it 
know that HTTPAPI means HTTPAPIR4?  Not everyone uses that naming 
scheme, obviously.

I also don't like each service program exporting a routine named 
'version'.  If every service program exports a routine with the same 
name, that's going to create conflicts.

You could name it "packagename_version" (where packagename is replaced 
by HTTPAPI in this example) that would be better... but still have the 
problem of connecting HTTPAPI with HTTPAPIR4.


> A question for Scott on version numbers. Was there a version 1.9 that came
> before 1.10? Are you following any particular version numbering scheme?

Honestly, I didn't give much thought to it.  The first version was 1.0. 
  Each new version I've released, I've incremented the part after the 
dot... so it became 1.1 - 1.23, etc.


> BTW, besides the callback routines in HTTPAPI, I didn't know true dynamic
> binds were available to us. I guess I missed the a couple of newsletters
> along the way. Doing some quick googling (QleActBndPgm) opened my eyes to
> this interesting technique.

Shrug...   it's not usually useful.   Most of the time, if you want 
dynamic binding, use a program instead of a service program.

However, I've been thinking about using dynamic binding for Expat, so 
HTTPAPI can detect at runtime if Expat is installed, and can even try a 
few likely suspects for libraries (i.e. if not found in *LIBL, also look 
in LIBEXPAT and LIBHTTP and use one of those.)  That way, you wouldn't 
have to compile HTTPAPI "with XML" or "without XML", it'd figure it out 
for you at runtime.

But I never got around to actually doing it :)
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------