RR as a browser plugin?
Christopher Mitchell
chrism at lumin.us
Wed Feb 11 22:55:04 EST 2004
So I guess then the distinction "brower plugin" implies it runs in a
heavily partitioned area that keeps it safe from being able to be
exploited to damage the system... that could still be useful but it is
probably easier or at least more useful to build the browser into Rev
than to build rev into the browser.
but for a bit of hope, I witnessed lots of women walking the streets
unescorted at night in Buenos Aires last summer. I will keep my
further comments mum!
Yours,
Chris
On Feb 11, 2004, at 9:08 PM, Richard Gaskin wrote:
> HyperChris at aol.com wrote:
>
>> Instead of a rev engine plug-in, I
>> want one that makes the following scenario happen ....
>> i roll out a web page with a link to my rev stack
>> that triggers a "plug-in required" the user accepts
>> the plug-in is downloaded
>> it launches and downloads the rev client app
>> AND (most importantly)
>> configures the browser to use the app as the helper for the rev type
>> the link to the rev stack now goes through and launches the rev
>> helper app
>>
>> That type of scenario cuts the roll-out cost of the app
>> significantly. IT
>> would not have to go around and configure everyone. If we can offer
>> that to
>> clients then we will be local heroes.
>
> Yes, that would be as desirable as women being able to walk city
> streets at
> night without escort. But sadly neither is possible, for the same
> reason:
> criminals abound.
>
> A system that could automate what you've described would also allow the
> automatic installation of any executable, including spyware, viruses,
> or
> more dangerous, Microsoft products.
>
> --
> Richard Gaskin
> Fourth World Media Corporation
> ___________________________________________________________
> Ambassador at FourthWorld.com http://www.FourthWorld.com
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
More information about the use-livecode
mailing list