Mike,I like your idea of a new 'version' or 'GetInfo' project. I do not know why I did not suggest that because actually I am thinking about something similar for my utilities. What I would like to have is a program that shows all my utilities in a subfile and let the user select the one he want to install. It should know all dependencies and download and install everything needed to fulfill
the user's requested.Once a utility has been installed the program should be able to check for updates and then install them if requested by a user.
Back to the 'version' command I wonder what Scott thinks about it.Dynamic binding is a powerful technique that gives us a bunch of new options. But it is not "the general way" to go. I use dynamic binding to let my Log4rpg dynamically bind to appenders, layouts and filters. The information what to load and bind to is stored in property files or members. Without dynamic binding Log4rpg could not be that powerful as it is.
Thomas. Mike Krebs schrieb:
Thomas and all, I like the direction you are headed here. Is it possible to take the "local" version command one step higher and do something like: Version('project') For HTTPAPI, it would look like this: version('HTTPAPI') and would return string value 1.23. The steps for version() would be similar to what you described. Using the parameter, we would have to dynamically bind to HTTPAPI and then return HTTPAPI_VERSION. Maybe what we need is a generic version() in each project. So, the steps would be bind to the project and call version(). Eventually, this could be extended to do this: version('http://scottklement.com/httpapi_version.xml') or maybe something like this: GetInfo('http://scottklement.com/httpapi_version.xml': 'version') that would recognize the http and go get the "thing" asked for in the second parameter. Then we could do this: If version('HTTPAPI') <> version('http://scottklement.com/httpapi_version.xml');Maybe this is a new project?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? 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. Mike Krebs
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
----------------------------------------------------------------------- This is the FTPAPI mailing list. To unsubscribe, please go to: http://www.scottklement.com/mailman/listinfo/ftpapi -----------------------------------------------------------------------