Hello, this exerpt from a previous post caught my attention:
I am distributing a web site that utilizes Zoom CGI through Server2Go. Our sales force is running the site from their hard drive because when on the road they frequently do not have access to the network.
The problem at this point is sending periodic updates. We have over 1800 files that Zoom indexes, which generates index files exceeding 20MB. I am able to create compressed files from 6-9MB, but that's still too large because many of our sales folks use dial-up connections.
Is there a way for me to install the indexer on Server2Go so that it's able to create a new index based on some sort of timetable or command trigger?
Then I would be able to send web site updates in the range of 200-500KB, which is digestible even for dial-up users, and have new index files generated on their end.
Thanks for your help and any ideas!
-Matt
If you have a Windows based server (and full control over the server) you can install the indexer directly on the server and avoid uploads of index files. Otherwise you need to run the indexer on another Windows machine (e.g. your desktop machine), create an index, then upload it.
The problem at this point is sending periodic updates. We have over 1800 files that Zoom indexes, which generates index files exceeding 20MB. I am able to create compressed files from 6-9MB, but that's still too large because many of our sales folks use dial-up connections.
Is there a way for me to install the indexer on Server2Go so that it's able to create a new index based on some sort of timetable or command trigger?
Then I would be able to send web site updates in the range of 200-500KB, which is digestible even for dial-up users, and have new index files generated on their end.
Thanks for your help and any ideas!
-Matt
Comment