I would recommend that you create a vfp mtdll to run as a service and use the ASP stub to call it. This will allow you to continue to use VFP and will be fast and scalable since it's multi-threaded..
>Hi all,
>
>
>In a few days I have to start a project to create our Webservice to control some internal procedures of our company..
>
>The subject of start a small (not very) Web solution by point 0, always makes me to imagine what really is the best decisions on the among of stuffs available..
>
>I mean a web server for HTTP, FTP, SMTP (and POP)..
>
>On Hardware decisions..
>
>. What is the best today's choice ? A good one computer or some of them divided by tasks..
>. What about the best conditions of this hardware, hi-spped SCSI/IDE disks.. Or what will makes on these servers the difference..
>. Connection.. Is it an ADSL (with 768k) a professional choice ?
>
>For software..
>
>. What is the best OS for that purpose ? I mean for good price (not cheapest), less support on handling, nice condition.. And to deal fine with VFP..
>. Is it MYSQL the really best data storage (on speed and safety issues) ?
>. What is necessary to integrate our VFP (the Eeta software company created some years ago a VFP Webservice application that allow us to use natural language of VFP by scripts inside of our HTML code).. Is it good ? Safety ? Fast ? Or there is something better ?
>
>My goal on this thread it is to share knowledge (and learn of course).. But, I believe this subject is still a lot of "on the hand" of few yet..
>
>Any commentary will be appreciated..
>
>TIA
>
>Claudio