Richard,
best way is not to generate the standalone and use the single file
stackfile, this way a simple GO STACK URL will do... if you must
generate a standalone, then zip it beforehand, then transfer, create
a routine that will unzip it and load, but that sucks because you'll
end up with duplicate memory use for engine since (it's two
standalones in memory), and the file will be bigger... and will not
be cross platform, using the plain rev file is better as it works
everywhere and loads faster.
cheers
andre
On Dec 18, 2005, at 6:12 PM, Richard Miller wrote:
I'm having difficulty downloading a Rev application from our
server. After trying the standard "put url" and LibURLDowloadToFile
commands, and not having those work, I've come to the conclusion
the problem is probably with the structure of a Rev-created
application (in that it's a package.... not just one file).
Apparently, those commands just can't grab the package.
I then thought about compressing the Rev app first using the
compress() commands, but "compress" doesn't seem to want to grab
the entire package either. So I'm stuck.
I could use Stuffit to compress the file on the server, but I would
need to unstuff it on the local side "on the fly" from within a
running Rev application... and that would appear to be a tricky issue.
Suggestions?
Basically, a Rev application on the local side needs to download a
Rev application from our server and then launch it locally. What's
the best way to do that?
Thanks.
Richard Miller
Imprinter Technologies
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
