From MemberWiki

URL: http://www.openajax.org/member/wiki/Interoperability_Minutes_2009-01-19

Contents 1 Attendess 2 Original agenda 3 Minutes 3.1 Rechartering 3.2 New table at top of Managed Hub APIs chapter 3.3 postMessage() 3.4 New pictures Managed Hub Overview chapter 3.5 Open issues and open tasks 3.6 Next meeting

Attendess

• Jon Ferraiolo, IBM
• Matthias Hertel
• Javier Pedemonte, IBM

Original agenda

• Agenda
  • Rechartering approved
  • Review recent spec editorial updates
    • Publish/Subscribe Overview chapter
      • http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Specification_Publish_Subscribe_Overview
      • Changes:
        • Replace "Mashups" with "Mashups (and other composite applications)"
        • Replace "widgets" with "components"
        • Add pictures showing (simple) Unmanaged Hub and (more complex) Managed Hub
    • Managed Hub Overview chapter
      • http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Specification_Managed_Hub_Overview
      • Changes:
        • Moved introductory sections about mashups into (new) Mashup Assembly Applications chapter
        • Redid Howard's module picture (moved from API chapter to here)
        • Removed Howard's interaction picture
        • Replace "widgets" with "components"
        • Redid picture that shows Managed Hub initialization and usage (align with Howard's color scheme)
        • Redid picture that shows Managed Hub message passing
    • Managed Hub APIs chapter
      • http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Specification_Managed_Hub_APIs
      • Changes:
        • Added class summary table at top
        • Added small sections on IFrameContainer and InlineContainer classes
        • Minor rearranging and cleanup
    • (NEW) Mashup Assembly Applications chapter
      • http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Specification_Mashup_Assembly_Applications
      • Changes:
        • Mostly cut/paste from content that used to be in Managed Hub Overview chapter
  • Review open issues
    • onComplete parameter proposal (Howard promised to send in a proposal, based on Javier's suggestion)
    • safeCall and safeDelete (Howard was going to study and get back to us)
  • Open tasks (i.e., actions not yet completed)
    • Reorder parameters to OpenAjax.hub.HubClient per Matthias's suggestion
    • For publish(), need to document what "*" means
    • connectToParent needs to be renamed to connect

Minutes

Rechartering

(Interop WG rechartering has been approved)

New table at top of Managed Hub APIs chapter

• http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Specification_Managed_Hub_APIs

Javier: Table looks OK. Need to add classes for IframeHubClient and InlineHubClient

Jon: OK

Javier: HubClient should be an interface that extends Hub. Clients invoke IframeHubClient.publish() or InlineHubClient.publish().

Jon: How do you know which to call?

Javier: That's an issue. Maybe we need a standard function that returns the appropriate class. Make sense?

Jon: Yes. That's an open issue.

postMessage()

Javier: I sent email internally at IBM on Friday about postMessage implementation. After studying the code, I understand things better. Some of the SMash code is for anti-pfishing. But postMessage() takes it into account via the 2nd parameter gives domain. But I'm unsure about posting a popup about frames going away.

Javier: I'll talk with the SMash authors this week. Their initial responses were that they agreed.

New pictures Managed Hub Overview chapter

• http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Specification_Managed_Hub_Overview

(looking at first picture)

Jon: I took Howard's module diagram and simplified it. I thought the side-by-side approach was somewhat confusing and better to simplify

Javier: Would be better to show the container somehow including both HubClient and the client component

Jon: The second picture now shows that. The first picture was simply to show the modules, with Howard's color coding to indicate which things are done by the app developer, which by the Hub, and which by the container developers.

(looking at second picture)

Javier: OK. But what about message flow between the components?

Jon: Look at the third picture. That shows message flow from a client component that publishes, through containers and Hub, back to a different subscriber

Javier: Just setting me up!

Jon: I got rid of Howard's interactions picture. It showed message flows, but we pretty much have that with the message passing picture.

Jon: Are the new pictures ok?

Javier/Matthias: Yes

Open issues and open tasks

(Walked through the list of open issues. Howard is supposed to make proposals on a couple of them. If he doesn't, then someone else will have to come up with proposals.)

Next meeting

Jon: Next week