> called it so(it's written in Delphi). So it isn't like he
> said, now i understand.
> The dll is called from the browser, that's a fact, in
> Dcomcnfg.exe you define access rights to this software so
> internet users can use it.That's all i know. And it runs via
> IIS5 on a win2k server. And there is nowhere a place in IIS
> where the dll is configured as a filter.
No, you're right, it is an ISAPI application; it's just not a filter.
> I've allready tried to call it with <cfhttp method="get"
> url="" but
> like i said before, the dll isn't working properly anymore.
Are you saying that the DLL doesn't work when invoked from a browser either?
> I allready suggested to the developer to work with web
> services, but they never heard about it before, so about
> building serious web-apps i don't have to discuss with them:
> they have their own vision :-(. To make my own interface and
> build another application beside the existing one would be
> like re-inventing the wheel, isn't it?
Yes, it would be like reinventing the wheel, but sometimes that's the best
option. In the long run, it would probably be better than using CFHTTP to
invoke an ISAPI DLL. Do you have the source code for the DLL? Do you know
what it does?
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
