Interoperability Minutes 2007-06-20

From MemberWiki

Jump to: navigation, search

Full minutes: /member/wiki/Interoperability_Minutes_2007-06-20

Contents

OpenAjax Alliance Interoperability Committee meeting minutes 2007-06-20

Attendees

  • Kin Blas <jblas(at)adobe.com>
  • Gideon Lee <glee(at)openspot.com>
  • Jon Ferraiolo <jferrai(at)us.ibm.com>
  • Greg Murray <greg.murray(at)sun.com>
  • Bruce Johnson <bruce(at)google.com>
  • Adam Peller <apeller(at)us.ibm.com>

Original Agenda

  • Agenda
    • Status report for finishing off OpenAjax Hub 1.0
      • All features implemented
      • Test suite: only thing missing are tests to verify filter as string (almost done)
      • Haven't started polish work on spec, but plan to finish complete draft within 2 weeks
      • Still recruiting people to integrate the latest Hub with their toolkits
    • AJAXWorld, demos, and getting the word out on the Hub
      • Jon is Technical Chair
      • Marketing WG and Steering Committee have talked about proposing an OpenAjax track at AJAXWorld
        • But what sessions?
      • Current thinking on demos
        • Demo #1 (possibly ends up being multiple demos): mashups using multiple Ajax toolkits
          • Highlight commercial adoption of the Hub? (TIBCO, Jackbe, QEDwiki, etc.)
        • Demo #2 (possibly ends up being multiple demos): (non-mashup) Web app that uses multiple Ajax toolkits
          • Highlight roll-your-own application with the Hub?
      • Getting the word out: blogs (by anyone), member product announcements, OpenAjax press release, ...?
    • SourceForge project
      • Any problems since the switch to the new URL?
      • Any suggestions about Jon's problem with TortoiseSVN?
    • Discuss Greg Wilkin's bridging proposal within CommHub Task Force
    • Hub event names: what charset to use?
      • Proposal: Just use whatever JavaScript 1.3 gives us (i.e., Unicode, usually as UTF-8, with escaping such as \uNNNN
      • Proposal: Topic names cannot use period (our separator character) or slash (to ensure 1-for-1 transformations with other pubsub systems such as Dojo)
    • OpenAjax Registry

Minutes

Topic: Status report on the Hub

All source code is done at this point

caveat find bugs. we'll fix them

features implemented all work, compact, may be able knock off another 100 bytes

3K in size

Test suite, a couple minor features not tested. Jon has tests for them but hasn't verified it.

Test suite is bascially done

Just need to finish spec:

examples

appendices

Next step, get people to use it in their toolkit.

Spry, Dojo, JMaki

GWT, may delay till 1.5, currently working on 1.4 release

Jon: Any updates on Dojo?

Adam: Heads down on beta release. No updates

Jon: JMaki?

Greg: Heads down doing 1.0 release. They have an extension api that will allow them to do this. They've been asked t o make it work in 1.0.2

Topic: Upcoming Ajax conferences

Jon: Next 'round of AJAX Conferences: AJAX experience, Web 2.0, AJAX World

Greg: JEZOON starts on the 28th

Jon: Marketing comittee trying to figure out what kind of demos and coordination they can get from the conferences.

Jon: Thinking of proposing a 1-day track on Open AJAX and have a whole days worth of OAA activities. Brainstormed some demos in conjunciton with activities.

Jon: Suggestion for a session on each comittee: Hub, Security, Communications, Mobile, etc. Do a functional break down and have the chair of each comittee do the session.

Jon: Anyone have comments, we'd love to hear it.

Topic: Demoes

Jon: With demos we're thinking their might be 2 clusters of demos: Mashups and non-mashup scenarios (AJAX and non-AJAX toolkits together)

Jon: Non-Mashup is where you have particular features like widgets from one, graphics from another.

Jon: Hilight commercial offerings that support the Hub and individual developer roles.

Jon: Synergistic marketing OAA and Vendor gets promoted if vendor shows OAA in their project. The hope is that Marketing folks will get demos together that show off integration.

Topic: SourceForge updated URL

Jon: Source forge changed their backend. New URL scheme to access their repository. June 29th the old URL swill no longer work.

Jon: Followed instructions and updated the project. Verfied new and old URLs still work with svn from the command line.

Jon: Anyone using Tortoise SVN? < no answer>

Topic: Communications Hub and proposed bridge

Jon: Next on the agenda Discussion about things going on in the Communications Task Force

Jon: Greg has sent in a proposal: Communications Events Proposal

Jon: Single bridge function that defines an event on the hub, whether the hub should bridge the event to other frames in the browser, or bridge it to other servers created via a comment.

Jon: Anyone have comments on the bridge method?

Jon: Example is a chat room. Typically its fine to go public. Chat room would then bridge to the server. Events published locally and bridged to the server.

Jon: Is everybody silent because they haven't read it or don't understand it?

Bruce: Not sure what its about.

Jon: Typical setup components to talk to each other within the same frame. Bridge extends publishing/subscribing into other frames.

Jon: Greg's proposals are appropriate. The Hub's pub/sub mechanism is currently designed for a situation is not concerned about security. For things where you don't want to broadcast in a public situation, then you wouldn't use this pub/sub scheme. Need to add frame to frame or single frame, single client to client apis so we don't do a broadcast. Some other technology plugs into the api and provides the service.

Jon: Frame to frame might be accomplished through sub spaces or dojo-like mechansim. Or hidden iframe. Implementation would be hidden but we define the api. And perhaps the w3c would come up with a standard which the browsers would implement.

Gideon: I think this approach is fine. Wouldn't it be better if the API used the same names etc.

Jon: Greg agrees that things need to be renamed and attached to the open ajax hub differently. We all agree changes have to be made, but we haven't agreed on what the changes should be. One proposal is adding a bridge method to the hub.

Jon: Greg was throwing out a draft with a general approach, and we would work out all the details.

Jon: Any other comments?

Topic: character set for event names

Jon: Last thing on agenda, What characters can you put in an event name? What seems obvious would be whatever JS gives us, which is Unicode presented with UTF-8, which also gives us the 16-bit unicode escaping mechanism with \u so that seems to me pretty obvious. Anyone see a problem with that?

Jon: Another topic event names any character can be used except a period. I propose we disallow a '/' since other toolkits use '/' as a separator. Disallowing '/' would be easier for toolkits to do the transformation of events from their topic system into our topic system. Dojo and Baiou uses '/'.

Jon: Baiou is client/server independent uses json syntax protocol. Is designed for low-level handshaking between client and server. Example stream is open, server can send data to the client. Stream is closed. Server can request stream be opened.

Jon: Its going in the right direction if it gets far enough, we may endorse it.

Gideon: How about double quote?

Jon: Same thing with single quote?

Gideon: It becomes hairy if you allow the quotes.

Jon: I'll send out an issue. Asking what's the harm in allowing/not allowing. Backslash is also not allowed.

Jon: Keep it simple and just not allow period and slash. And otherwise let people hang themselves. I'll send out an issue.

Topic: Next meeting

Jon: 2 weeks from today is a US holiday so I propose we have our next call on July 11th. Main topic is going to be the OA registry. We did the process stuff in a previous call. Focus on defining the criteria by which we decide, what type of global names we allow, we allocate particular things to a particular toolkit. Overall architecutre of how we go about doing things.

Retrieved from "/member/wiki/Interoperability_Minutes_2007-06-20"
Personal tools