BOBSCOTT wrote on Oct 5
th, 2011 at 7:12pm:
Mark,
Thanks so much for the input. I value your guys advice and guidance very highly. With your statements and my lack of knowledge on the subject, I will for now just continue with my cloud based drive set-up that is very secure and works well with Sesame even if it seems a bit Rube Goldberg ish.
What about using the cloud server is striking you as clumsy? Most of the impediments to serving files on the internet are there for security. If security is no issue...
For example, using your router's ability to allow a computer to be placed directly on the internet using a static IP address. You could place a computer that has only the files you wish to be shared and an OS. It must have no other network access. As long as these files do not need to be secured, everyone on the internet could access those files. Hackers could, of course, gain access to that one computer, but since it doesn't attach to any others, no harm done. At worst they might bring down the machine or infect it and it alone - inconvenient, but not a disaster.
The problem comes up when you only want to share
some of the files with only
some people. Now you need a way to identify the people (passwords, encryption, etc...). You need a way to keep the people who are allowed on in only the directories they are allowed to see. If you put a computer directly on the net, you have to set all of that up. Even experts worry about that kind of arrangement, and are constantly battling the hackers.
Having a cloud based server provides a shared filesystem that is protected by a third party. So, while you will have to trust that they know how to do their jobs, it is their job to worry about break-ins so you don't have to.
BTW: if your company is already running a web server, you can place these files in a directory under the public directories but not linked to any web page. Put an index.html file in that new directory that is entirely blank (to protect the files from browsers and search spiders) and then use a free utility like "wget" or "synch" from each of your clients when they start sesame to download the files to a local directory, if they aren't too big. Then your SBasic simply accesses the updated files locally.