Hi all!



I was just wondering about a thing...



Have you encountered, during development, the limitations with the fso in

ASP?



I am talking about the missing binary capabilities of the VbScript fso.



1. Would it be interesting to find out how to solve it?



2. Would it be interesting to read about it?



3. Would it be nice to have a wrapper class, which has additional methods

like "fso.openBinary(...)" or "fso.saveAsBinary(...)" and so on?



Maybe, the world has already solved this problem. Maybe, it's just me that

have not found the right places to look for the solution.



This might be interesting to the editors of ASPToday as well...?



I'm thinking of creating a wrapper class that has these additional binary

methods and maybe all the other methods and properties. Maybe it would be a

little stupid to wrap all the other things that the fso provides, but my

thought was that, if you do that, you have everything in one place.



Of course, this is mostly needed when you not are able to install your own

objects on the server since there is easy VB solutions to this. 



The reason why I started thinking about this is that a friend of mine asked

me how to get binary files that was not visible from http and send them to

the client. He could not use COM. I made one solution with ADO.Stream but

that required ADO 2.5, which his client didn't want to install. The only

thing that was left was the fso, so I made a solution with that instead. 

That gave me this idea. Could it be interesting to read about it, or is it

out of date? 



I have reason to think that it could be quite interesting, cause articles

like that was the ones I appreciated a lot on ASPToday.



What do you think?



Thank you.



::micke