Posted by StupidScript on 09/09/05 22:01

I like (3), Carl. I may have had it bass-ackwards. I'll work on the
approach suggested by (3), I think.

As an explanation:

I'm working on an app to be delivered over the web. I need centrailized
control to update major portions of the app's interaction with many
vendors. The app will use several very large files, like big VR files
and high-res graphics that would be tedious to download each time the
user wanted to work with their customized instance of the app. These
large files are static, and they interact with the app's
vendor-supplied data in such a way as to give the user current options
for the display and modification of their "project". I thought I'd put
the big files and various static stuff onto CD/DVD and deliver those to
registered users to (a) minimize the bandwidth required to work with
the app content and (b) maintain some measure of control regarding
which users have access to the full-blown app capabilities (deter
unauthorized app access ... as, without the disk, an unauthorized user
would have little to work with).

I'm thinking, now, of placing an XAMPP (or similar) installation on the
CD along with the big files and such and running the base app from the
client, pulling updated, centralized content from the server under some
auth scheme. Maybe I won't need it, but it gives me more options than I
had with the other idea. Thanks for the suggestion!

[Back to original message]