> The idea to keep incrementing the file sounds good, and I could do it > on the upload end, but I am not sure on the browser end to keep making > the browser get the latest, or second latest file on the website. I > am using this type of HTML command in the page to make it refresh > automatically in the browser: > > <meta http-equiv="Refresh" > content="2,URL=http://www.members.shaw.ca/roger.zimmerman/ > sharedesktop/refresh.html"> > > Where the 2 sets the delay in seconds before a refresh. And within the > refresh.html page it puts up an imaged called something like > screenshot.jpeg. The screenshot.jpeg gets set to 0 bits right on my > website, so there is nothing the browser can do anymore to get it. It > stays at 0 bits, even after I stop the browser and stop the automated > ftp code from putting a new screenshot.jpeg up on the site. The next > time I run the ftp code (without the browser running), the > screenshot.jpeg gets updated correctly on the site (except > ocassionally I need to delete screenshot.jpeg first then run the > automated ftp code). > > Here is what I am using for the automated ftp code, I have tried > "send" in a loop or just copied the Send command over and over for > now. I commented out the loop I used to use, because it had to keep > opening and closing the connection every time it did a send. Any ideas > to fix that loop so it doesn't have to open and close the connection > each time is also appreciated: > ____________________________ > > #!/bin/sh > > HOST='ftp.shaw.ca' > USER='roger.zimmerman' > PASSWD='password' > > # echo -n "aftervariables${i} " > > #for i in $(seq 1 100) > > #do > > ftp -n ftp.shaw.ca <<SCRIPT > user $USER $PASSWD > send screen2.jpeg /sharedesktop/screen2.jpeg > send screen2.jpeg /sharedesktop/screen2.jpeg > send screen2.jpeg /sharedesktop/screen2.jpeg > send screen2.jpeg /sharedesktop/screen2.jpeg > send screen2.jpeg /sharedesktop/screen2.jpeg > send screen2.jpeg /sharedesktop/screen2.jpeg > quit > SCRIPT > > #done > > exit > > _________________________________ Ok, What about something on these lines then: upload your file naming it whatever1.jpeg, whatever2.jpeg, whatever3.jpeg etc up to say whatever10.jpeg and then starts from whatever1.jpeg again. Find out how long it takes to upload the file. Create 11 pages on your friends PC each one should have a timer ( the refresh ) to wait long enough so that the next file has enough time to upload completely. Page 1 should just wait until the first file is uploaded and then go to the next page. Each of the other pages should load a different .jpeg file ( 1 to 10 ) Then page 11 should point back to page 2 ( which should load whatever1.jpeg ) and so on.
Exactly how you would implement this depends on your webserver and what facilities are there. php springs to mind as something you could embed in the pages. In fact I suspect that with php you could just have one page and load different pictures into it on a cyclical basis. it's a while since I did anything with php so I don't remember exactly what it can do. If it can get the file size then that would probably work. Anyway if I can think of other ideas I will let you know. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ubuntu Linux" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubuntulinux?hl=en -~----------~----~----~----~------~----~------~--~---
