My Windows application has MapPoint ActivreX tightly integrated to perform address lookups, travel times and distances, and to provide a map to the user, with the user's current information displayed. But I need to quickly develop an ASP version of my prorgram, and wonder if I will need to abandon MapPoint to make the tranisition.
The MapPoint webservice is not an option for me, due to the high cost per lookup. I operate in a very low margin business and do a lot of lookups, so even 1.6 cents per lookup breaks my cost model.
I have flexibility about the number of machines I'll be running. So does it make sense to have a dedicated Windows machine which uses the ActiveX control to provide my ASP program with addresss lookups and travel times lookups? That would fit nicely into my cost model since a slow machine can do 5-10 lookups per second. I could start with a slow machine and scale up as needed. Would this violate the license? It would be a single machine, yes, so in that sense would not violate the license. But it may be a violation, like trying to use a VCR to show a movie to a crowded movie theater. That's against the rules, and using a single Windows machine to process (for free) address lookups for a bunch of different location may be also a violation, but I hope to hear other people's opinions.
In addition to the issue of rights, how would I do it technically. I'm new to ASP, and wonder would I connect my ASP app. to the computer running MapPoint? Would I need to make a web service? Could I just map a drive and write the lookup results to a shared file?
And lastly, what about providing mapping via ASP? How might that work?