Re: Puzzled by the demos

On 2/13/2012 11:02 AM, John J Barton wrote:
> On Mon, Feb 13, 2012 at 10:51 AM, Paul Kinlan<paulkinlan@google.com>  wrote:
>> I added Content Security Policy to the shim and a lot of the demos have
>> stopped working in FF until I get that fixed.
>>
>> wrt Chrome right at this moment you need to install apps from the CWS first
>> - Ideally this would never be the case because we can detect apps via the
>> presence of a tag.
> I was hoping the demo would clarify the intro page:
>
>      Services register their intention to be able to handle an action
> on the user's behalf.
>
> Where are these 'services' ? On web sites? On pages in the users
> browser? Chrome apps? How do they get registered?
>
> The other question I was hoping to answer by inspecting the demo:
>
> What web pages / iframes are involved in the overall process?
>

Services are on websites, found via <intent> tags in the content body.

Chrome just went through some updates (hello unstable!) which may make 
things a little more confusing.

In Paul's shim, he scans for intent tags, submits them to a 
session-based page, and adds a JS shim for various methods. When intents 
are invoked, the session based page pops up with a list of items that 
match the invocation. You select an item, and it handles all of the 
postMessage dynamics.

Frame (a) registration via <intent>, saying which intents are supported 
by which page..
Frame (b) intent registration shim. Frame (b) would normally be handled 
by the browser, natively.
The user keeps on trucking until they reach frame (c); a page which 
invokes an intent, such as share.
They activate that invocation which pops up Frame (d), an intent 
selector shim. Frame (d) would also be part of the browser.
They use that intent selector, which will pop up frame (e), possibly the 
same url as frame (a), certainly the same domain.

Communication happens, a message is handled to connect frame (c) and 
frame (e).

-Charles

Received on Monday, 13 February 2012 21:50:57 UTC