Interoperability Minutes 2007-01-17
From MemberWiki
Full minutes: /member/wiki/Interoperability_Minutes_2007-01-17
OpenAjax Alliance Interoperability Committee meeting minutes 2007-01-17
Attendees
- Adam Peller <apeller(at)us.ibm.com>
- Alessandro Alinone <alessandro.alinone(at)lightstreamer.com>
- Alex Russell <alex(at)dojotoolkit.org>
- Guido Laures <Guido.Laures(at)softwareag.com>
- Ingo Muschenetz <ingo(at)aptana.com>
- Jon Ferraiolo <jferrai(at)us.ibm.com>
- Ken Tam <kentam(at)bea.com>
- Louenas Hamdi <louenas.hamdi(at)sap.com>
- Rick Evans <Rick.Evans(at)Sun.COM>
- Shailesh Hingole <shingole(at)gce2000.com>
- Simone Fabiano <simone.fabiano(at)lightstreamer.com>
- Ted Thibodeau <tthibodeau(at)openlinksw.com>
Original Agenda
- Agenda
- Begin a walk through of the OpenAjax Hub Specification
Minutes
Topic: Abstract, Status of this Document
Jon: Talks about OpenAjax Conformance OpenAjax Alliance mission and status of the document. No questions about these topics.
Topic: Table of Contents
Jon: Goes over the table of contents and gives a brief introduction about each chapter.
Topic: Introduction
Jon: First three sections copied from public website. Goes over the major features included in OpenAjax Hub.
OpenAjax Conformance: No centralized listing of all the requirements required by a library to become compliant. Points out the general format for specifying requirement.
OpenAjax Conformance Requirement (<category>): <name>
Goes over the different use case scenarios. Make sure hub can be embedded in Ajax Library. Went through the different scenarios and examples of each of them.
Topic: Libraries Interaction with the hub
How the libraries should handle the loading of hub. Ex. If hub is being loaded before yahoo toolkit then it must use this hub instead of reloading it.
Alex : It is unrealistic to expect the vendors to write code for different use case scenarios like when to load/skip the hub.
Jon: Identify this as an issue. Dojo is planning to include it own implementation of hub. You use it or not. We leave this as it is for now and put it as item to research.
Topic: Prefixes, Namespaces, Global Objects, Multiple Usage
Jon:Explains how a library should define a prefix and register with OpenAjax library. Library should be responsible for handling this scenario. No specific implementation details provided.
(Question from someone): Do we support multiple versions of same library one of which is not OpenAjax compliant.Ex. I am using a newer version of prototype which is OpenAjax compliant but at the same time I am using a component that uses older version of prototype which is not compliant.
Jon: This scenario is not supported. We will only consider cases where all the participating libraries are OpenAjax compliant.
Reference implementation and test suite
?? : Did you integrate prototype with OpenAjax hub?
Jon: Not made much progress in it.
Topic: Library Management
Jon: Went over the registerLibrary API. General agreement that the version numbers should be numeric and in the form #[.#]. Any build specific or milestone information like (beta or alpha) and other tags should go in extra data.
Shailesh: Who is responsible for calling unregisterLibrary library API ?
Jon: Does not seem like an API that can be called too often. Mostly useful for testing purposes.
Is it mandatory to call unregisterLibrary ? No
Topic: Globals Management
Jon went over the API's. General agreement that collison check is not bad whenever a library registers for globals.
Topic:Load Unload Management
Methods are mostly unchanged based on what Alex contributed. Jon added phase parameter because he encounterd timing issues while testing. Explained the phase paramter using an example.(Datagrid that uses yahoo toolkit).
Jon to Alex: Question about refOrName/scope. When going through the source code, as soon as the function is called, the code immediately resolves the pair into a function reference. Shouldn't it be implemented instead using late binding?
Alex: Yes.
Jon: I will change the code to use late binding.
Topic: Publish/Subscribe
Alex's originial code submitted in May. Main difference that Jon added was the notion of subscriber data and publisher data. Both of these are extensibility mechanisms. Methods are clean and simple.
Jon: Cut out the wildcard for publishing events because of difficulty in implementing and couldn't see compelling value.
Shailesh: Any standard event names ?
Jon: Supported the idea of using standard event names. Example: openajax.drag for drag event. Can be considered as an addition down the road.
Jon: Tibco is implementing the hub. Interested in more flexible use of wildcards
Alex: Issues with Greedy/Non Greedy pattern matching in javascript.
Jon: Yes. I would think that you would leverage reg expressions for any pattern matching. Also, overlap with the filter feature that we have. Conceivable, could subscribe to "*" with a filter that examines the event name leveraging reg exp.
Jon: Concluded the session. Next time will be covering the remaining topics, starting with the Markup Scanner.
