System messages should be pluged into the application manifest #73

Activity

1. ghost assigned

   mounirlamouri

   on Apr 16, 2013
2. marcoscaceres commented on Apr 16, 2013

   

   marcoscaceres

   on Apr 16, 2013

   Contributor

   More actions

   Can you clarify what you mean by "plugged"?
3. mounirlamouri commented on Apr 16, 2013

   

   mounirlamouri

   on Apr 16, 2013

   ContributorAuthor

   More actions

   In Firefox OS we have:

   "messages": [
     [ "foo", "/index.html" ],
     [ "bar", "/blah.html" ]
   ],

   The current spec doesn't say how you register to get system messages.
4. jmajnert commented on Apr 17, 2013

   

   jmajnert

   on Apr 17, 2013

   More actions

   OK. So the setMessageHandler() doesn't actually register for a message? It only sets a handler for messages that the application had previously registered for via the manifest?
5. mounirlamouri commented on Apr 23, 2013

   

   mounirlamouri

   on Apr 23, 2013

   ContributorAuthor

   More actions

   Yes.
6. jmajnert commented on Apr 24, 2013

   

   jmajnert

   on Apr 24, 2013

   More actions

   OK. Then I think we should clarify that in the runtime spec. The current text gives no hints as to how registering happens.

   Why do you think the system messages should be declared in the manifest? Wouldn't a runtime API for registering/unregistering be enough?
7. mounirlamouri commented on Apr 24, 2013

   

   mounirlamouri

   on Apr 24, 2013

   ContributorAuthor

   More actions

   We might need a runtime API too but we definitely need something in the manifest so I prefer to delay the JS API for when we will really need it.

   I started writing something for that last week. I have to find time to finish it.
8. jmajnert commented on Apr 25, 2013

   

   jmajnert

   on Apr 25, 2013

   More actions

   From the example you gave earlier I see that the registration is on a per-document basis - message of type "foo" goes to index.html and "bar" goes to blah.html. Could you please explain what the expected behaviour is if a "bar" message arrives when:

   1. Application is not running (its manifest says "launch_path: 'index.html' "). Will the application launch normally and get redirected to blah.html (at what point?), or will it launch directly with blah.html?
   2. Application is running, index.html is loaded. I guess the system message will have no effect until user navigates to blah.html?
9. jmajnert commented on Apr 29, 2013

   

   jmajnert

   on Apr 29, 2013

   More actions

   I think this issue is also relevant here: #20
10. jmajnert commented on May 10, 2013

    

    jmajnert

    on May 10, 2013

    More actions

    We should also consider multi-window scenarios as in #100