Interoperability Minutes 2009-03-09

From MemberWiki

Jump to: navigation, search

URL: http://www.openajax.org/member/wiki/Interoperability_Minutes_2009-03-09

Contents

Attendees

  • Jon Ferraiolo, IBM
  • Javier Pedemonte, IBM
  • Eduardo Abe, IBM/ILOG
  • Rama Gurram, SAP

Original agenda

  • Agenda
    • Specific topics
      • Finally ready to change version from 1.1 to 2.0?
      • Create a build process that merges the relevant files and minifies the code?
      • Should the Unmanaged Hub code be included as part of Hub 1.1 code, or separate file?
      • Rename smash.js to FIM.js?
      • Proposal: We have multiple flavors of Hub 1.1/2.0, including: 
	release/all:
		OpenAjaxManagedHub-all.js
	release/std:
		OpenAjaxManagedHub-std.js
		FIM.js
	release/core:
		OpenAjaxManagedHub-core.js
		inline.js
		iframe.js
		FIM.js
	release/unmanaged-hub:
		OpenAjaxUnmanagedHub.js

Minutes

Rename Hub 1.1 to Hub 2.0

Rama: Better to use Hub 2.0. We have a lot of changes. The sooner the better.

Eduardo/Javier: Agreed

Jon: Howard wanted to wait until we were closer to the end of the process. I think we are now ready.

Rama: Why wait?

Jon: We decided to wait at the last face-to-face meeting to minimize confusion since lots of people were aware of "Hub 1.1".

Rama: It's a working spec. Shouldn't impact anything in production.

RESOLUTION: Change to 2.0.

Releases

(Discussion of the following things from the agenda)

  • Create a build process that merges the relevant files and minifies the code?
  • Should the Unmanaged Hub code be included as part of Hub 1.1 code, or separate file?
  • Rename smash.js to FIM.js?
  • Proposal: We have multiple flavors of Hub 1.1/2.0, including: 
	release/all:
		OpenAjaxManagedHub-all.js
	release/std:
		OpenAjaxManagedHub-std.js
		FIM.js
	release/core:
		OpenAjaxManagedHub-core.js
		inline.js
		iframe.js
		FIM.js
	release/unmanaged-hub:
		OpenAjaxUnmanagedHub.js

Jon: We have a mini build process right now. Simply concatenates JavaScript files into a single file.

Jon: Javier's proposal is as follows:

  • "all" includes everything in one file
  • "std" splits off FIM.js. This looks ahead to when old browsers are eliminated and all browsers support postMessage()

Javier: The FIM.js file is about as large as the rest of the Hub

Rama: How does the choice between FIM and postMessage work today? Is it automatic?

Javier: The IframeContainer code looks at the browser environment to see if postMessage is there. If not, use FIM

Rama: What about window.name?

Javier: You can add that by building a custom container

Jon: Not that the releases we create do not prevent people from creating whatever configuration they want

Jon: Who would use "core"?

Javier: Allows people to more easily roll their own. For example, maybe no inline.

Javier: Should we make multiple ZIPs? That would allow us to track who uses which.

Jon: Not a reliable statistic.

Javier: Yes, but maybe there is some value in tracking.

Jon: The "unmanaged-hub" release is our answer for people who just want intra-frame messaging with the same footprint as Hub 1.0, but want to use the latest and greatest code from OpenAjax. OK with everyone?

Rama: Yes

Javier: Good starting point. We can tweak.

Review of red-colored items in Managed Hub APIs chapter

Javier: Have to wait on Howard. He has made lots of updated recently.

Retrieved from "http://www.openajax.org/member/wiki/Interoperability_Minutes_2009-03-09"
Personal tools