Interoperability

From MemberWiki

Jump to: navigation, search

Contents

[edit]

Interoperability Committee Home Page

[edit]

Logistics

[edit]

Email list

The email list for the Interoperability Committtee is interop@openajax.org. Archives can be found at: http://openajax.org/pipermail/interop/. To subscribe to this list, fill out the form at: http://openajax.org/mailman/listinfo/interop.

[edit]

Next meeting

NOTE: At this time, this wiki page only includes the schedule for the Interoperability Committee phone calls and does not show the times of any Task Force (IDE TF, Server TF, Communications Hub TF or Security TF) phone calls. Refer to those pages for the schedule of upcoming phone calls for the task forces.

  • Next meeting: Wednesday March 7, 8amPST, 11amEST, 5pmParis
  • Dial-in Number(s):
    • Toll Free: 1-877-422-0052
    • Toll: 1-314-655-1417
    • Participant Pin access code: 142380
  • IRC channel: irc.freenode.net, #oaa-interop
  • Agenda
    • F2F meeting - Register or starve
    • AJAXWorld press release and placard around InteropFest
      • If you want to participate in the press release, need to get going
    • Recent changes to spec and open source
      • Late binding of refOrName/scope finally implemented
      • Got rid of modules Libraries and Globals (not part of core)
      • Added module Collision
      • checkForCollisions() now returns an array that lists the collisions that were found
    • Small Hub change to discuss
      • OpenAjaxConfig.bootstrapFile becomes OpenAjaxConfig.modDir (directory where JavaScript for other Hub modules can be found)
    • James' performance investigations and proposed source code changes
    • Discussion of other issues raised by John Resig (http://ejohn.org/blog/thoughts-on-openajax/)
      • 38.3kB uncompressed and about 7kB
      • Waiting for window.load event not always the best thing
      • Use of window.attachEvent() instead of addEventListener
      • Markup scanner defines its own markup selector APIs instead of using standards
      • His recommendations:
        1. Use DOM event listeners in your code.
        2. Use a DOM Ready implementation to avoid using window.onload
        3. Use simple DOM queries to locate your pieces of markup (getElementsByTagName).
        4. Never overwrite any global variables.
        5. Keep your code confined to a single, global, namespace.
[edit]

Ongoing

  • Regular teleconference schedule: every other Wednesday, 8amPST, 11amEST, 5pmParis. Dec 20, (skip a week) Jan 10, Jan 24, etc.
[edit]

Task Forces

[edit]

Documents

[edit]

Recent

  • Interoperability Communication - Initial page describing background information and proposals for adding communications/messaging features to the OpenAjax Hub
[edit]

Older

  • OpenAjax Hub - Executive summary of OpenAjax Hub for posting on our web site
  • Markup Scanner - James Margaris has developed some very early JavaScript for the OpenAjax Hub for people to review.
  • OpenAjaxHub Ideas 20060719 - Here are some concrete proposals for the OpenAjax Hub in the areas of JavaScript collision detection, toolkit loading, markup mixing (for consideration by the Markup committee), and event management.
  • Interoperability State of the World - List of scenarios today where toolkits interoperate successfully and where interoperability falls short
  • Markup Mixing Nexaweb IBM 20060712 - This is a link to a working document from the Declarative Markup committee which contains a recent attempt to capture current thinking in that committee about how to achieve interoperability at the markup mixing level. It is relevant to this discussion because it talks about features and issues within the OpenAjax hub.
  • OAH Proposal:
  • Alternate Hub Proposal Using XML Namespaces - Here is a proposal that attempts to provide the same functionality as the Tibco/Dojo proposal but expresses the markup in a manner that attempts to channel the spirit of W3C's architecture vision and thereby leverages XML namespaces. Not sure if this is a good idea or not, but here it is for people to review.


A related technology effort is the XAP proposal that is now an incubator projects at apache.org. Here is a wiki page that provides an executive summary of XAP and includes links to detailed information on XAP:


James Margaris of Nexaweb pointed out that we need to have a clear definition of what we are trying to accomplish. Here are notes, which are mostly directed at the issue of markup mixing:

[edit]

Other Information

(We need to define roadmap and schedule. )

Retrieved from "http://www.openajaxalliance.org/member/wiki/Interoperability"
Personal tools