D
Derek Timothy
Hello All,
I have written a little VB program to send packets of data to my web server
every 5 seconds in the form of a small csv file. The idea is to have a live
(or almost live) "call status" web page running in ASP making use of the
data in the csv file.
So what I have done it to write a service in VB on the server that looks for
the csv file every 5 seconds and if it is found it creates a new asp page
with an autorefresh meta tag and copies it to wwwroot. It is virtually live
and my manager from anywhere in the world can see the status of service
calls.
I think it is a good idea but my programs hang after half an hour and I am
beginning to wonder if I have some sort of locking issue or if I am going
about this the right way.
I had thought of scrapping the service part altogether and just using a
single ASP page with an autorefresh that reads in the csv file data using
the FileSystem object, but surely that could be at risk of locking problems
as well (if the FTP were trying to overwrite the existing file, while the
asp page is trying to read it). Perhaps not, I'm not sure. Really I'm just
looking for re-assurance that my new idea will work before I go too far down
the wrong path. If not, any other ideas or tips would be much appreciated.
Best Regards,
Derek
I have written a little VB program to send packets of data to my web server
every 5 seconds in the form of a small csv file. The idea is to have a live
(or almost live) "call status" web page running in ASP making use of the
data in the csv file.
So what I have done it to write a service in VB on the server that looks for
the csv file every 5 seconds and if it is found it creates a new asp page
with an autorefresh meta tag and copies it to wwwroot. It is virtually live
and my manager from anywhere in the world can see the status of service
calls.
I think it is a good idea but my programs hang after half an hour and I am
beginning to wonder if I have some sort of locking issue or if I am going
about this the right way.
I had thought of scrapping the service part altogether and just using a
single ASP page with an autorefresh that reads in the csv file data using
the FileSystem object, but surely that could be at risk of locking problems
as well (if the FTP were trying to overwrite the existing file, while the
asp page is trying to read it). Perhaps not, I'm not sure. Really I'm just
looking for re-assurance that my new idea will work before I go too far down
the wrong path. If not, any other ideas or tips would be much appreciated.
Best Regards,
Derek