Pancake/French Toast/Message API: Difference between revisions

Pancake/French Toast/Message API (view source)

271 bytes added , 12 September 2012

Confirmed users

31

edits

Revision as of 10:37, 12 September 2012 (view source) Sfoster (talk \| contribs) (→‎As a front-end developer, I need the app to tell me when a layer has received focus so that I can check for updates and refresh data if necessary.) ← Older edit		Revision as of 10:42, 12 September 2012 (view source) Sfoster (talk \| contribs) (→‎Discussion) Newer edit →
Line 53:		Line 53:

	''I don't think we need a general message mechanism to talk to the app. I also don't think we need to be able to send messages to specific layers from specific layers. In general, I would like to make the coupling between layers loose, and based on requesting URLs be opened. The layer itself can decide what to do with the URL.'' -[[Gbrander]]		''I don't think we need a general message mechanism to talk to the app. I also don't think we need to be able to send messages to specific layers from specific layers. In general, I would like to make the coupling between layers loose, and based on requesting URLs be opened. The layer itself can decide what to do with the URL.'' -[[Gbrander]]

			''Agreed that urls should be the primary messaging mechanism. We also have storage events which (browser-support willing) should allow us to signal state changes like login/logout across windows/layers. I suspect there's still a need for the native/js messaging though.