On 11/28/06, Charlie Coleman <[EMAIL PROTECTED]> wrote:
>
> But then the dependency would be on external .exe's correct?

And the difference between that and ActiveX controls is ...? <g> Same thing.

I believe that if you look around, you would find a version of wget or
curl compiled into a DLL that could be integrated directly into your
application.

If you depend on an ActiveX control, you are depending upon entire
frameworks of Microsoft code that are continually patched, modified
and "secured." I feel that limiting your dependence to a single DLL
you have complete control over is preferable to depending on Microsoft
not to decide that FTP'ing is insecure and should be blocked. After
all, that's likely the way a lot of malware updates itself.

> IIRC wget is
> more for background processes like keeping FTP mirrors in sync, etc.

wget just gets a file. How you use it is up to you.

> In our
> design, doing the download is a specific, directed request, and only for
> something that needs updating. Note that the file being downloaded does not
> remain: it is a .zip file - it's contents are extracted and it is deleted.
>

So you could issue (psudo-code, I don't know if this exists):

!/N wget.exe https://www.example.com/yourfile.zip

or:

Declare Boolean GetTheFile(filename as string) in wget.dll
GetTheFile("https://www.example.com/yourfile.zip";)

> I've never been really liked trying to integrate external .exe's with my
> systems.

Me, neither. The MS Office Desktop ODBC drivers (these are exes)
nearly cost me my job when they "upgraded." I'd prefer to have files I
am control over.

> Lastly, this one particular client is a MS-head-shop. It has been pretty
> tough keeping VFP going with these guys. So I doubt that I could get past
> stage 1 with anything else non-MS.

Well, perhaps Microsoft will offer a version of OpenSSH. Of course, it
would probably require the DotNet runtime <g>...

> We don't really have any problems with using the OCXs. They do need to do
> the 1-time install, but things are good to go after that.

My concern is trusting Microsoft to continue to support your OCXs. Not
from malicious "Let's screw over Charlie and his OCXs" as much as "we
don't think anyone is using this functionality and have decided it's
insecure, so we'll turn it off."

> If MS's OS wasn't so crappy, the whole 'lockdown' thing wouldn't be an
> issue. It's sort of a nice reminder that people shouldn't be using Windows
> anymore.

Well, if you're not part of the solution, you're precipitate.

-- 
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to