|
Post by tnorvell on May 24, 2008 14:22:22 GMT -5
What is the easiest way to take an ASCII file that resides on the webserver executing RunBASIC and have the .BAS program transfer it to the client's C: drive.
For example, I want to create a print job on the server and transfer it to a specific folder on the client's C: drive.
I've been thinking about writing an FTP client software that periodically polls an FTP account for new files.
I've also thought about passing data back and forth using the an XML challenge and response.
I do not want to map drive letters to the webserver (because of the expensive licensing issues with Microsoft server products)
I do not want files to take longer than 1 minute to begin transferring.
Any ideas?
Perhaps RunBASIC could have a command called OPEN CLIENT "filename.ext" FOR INPUT/OUTPUT/APPEND AS #filter and there could be an add-in for the web browser?
|
|
|
Post by StefanPendl on May 24, 2008 17:37:30 GMT -5
Browsers are not allowed to save files to a location on the clients drive automatically. The user will have to download the files with the browsers capabilities. html "<script type='text/javascript'> window.print() </script>"
You should be able to use the above to print the current browser window or tab.
|
|
|
Post by tnorvell on May 27, 2008 12:16:51 GMT -5
Actually, I was just using a print job as an example. I ended up writing a server app (for the webserver with RunBASIC on it) and a client app (for the client) that periodically polls a folder through the listening server app.
I wish I could do all of this without resorting to Microsoft products. A great language enhancement would be a command or webbrowser extension that would allow RunBASIC programs to initiate a file transfer to the client.
I am really impressed with RunBASIC reliability - once you learn the little stuff to avoid, it's very responsive and stable.
|
|