Communications Hub TF Minutes 2007-01-24

From MemberWiki

Jump to: navigation, search

January 24 2007

Attendees: Alessandro Alinone(lightstreamer), Simone Fabiano(lightstreamer), Jon (IBM), Coach (Nexaweb), Ted Thibodeau(Openlink), Alex Russel(Dojo/Sitepen). Ted (IceSoft), Greg Wilken(WebTide);


  • Agenda
    • Introduction
    • How to take the task force to the next step (or what is the next step)? For example, when is the appropriate time for the task force to be absorbed into the general interop?
    • The task force in general agreed with Greg's proposal last year and Greg has been making some good progress since then. Let's review this and gather feedback
    • Any Other Business
    • Wrap up

Topic: Task Force Status

Jon: Greg has filled in the form and willing to consider his code contribution under Apache license. But Greg is not a committer yet;

Alex: I recommend Greg to a committer;

Coach: i support this proposal;

Jon: I'll contact James Margaris on this. so that Greg can contribute his code;

Coach: Jon, what is the right process that we should follow to complete the mission of the task force?

Jon: we are a new organization and we are exploring. We should explore and have a prototype, and then recommend the prototype to the committee;

Jon: the next question is "how far the prototype should go"?

Jon: We should play by ear.

Coach: I'd recommend we follow the existing path, do bi-weekly conference call, until we have reached a prototype and think we are ready to make recommendations to Interop committer. Do people agree?

Various people: yes.

Topic: Technical

Alex: I saw one of the Cometd contributors did something very decent to solve the "two connection" problem. For long live connections, it will be very handy if there is a way for a page to say "yes, i opened a long lived connection to a server or not". On IE, there is user data; on Firefox, there local storage. Both can be used to keep such infomation available so that no need to open more than two long lived connections to the same domain.

Jon: any security concerns that have been looked into?

Jon: a lot of this can be very well handled within the messaging API. /member/wiki/Greg_Wilkins_API_Proposal;

Ted: the central question is whether we should have an API very similar to XHR or some different messaging oriented API.

Alex: I am looking at Greg's API proposal. like pub/sub in general. But it may not be good for the general request/response paradigm;

Greg: I am thinking of the same question recently. I think we should have both: an XHR-like API for request/response; and an messaging oriented API for pub/sub kind of communications.

Alex: one can imagine a request/response publish to a channel. But at an API level, it is separate.

Greg: i think the API should be semantics only. and leave all the transport to the implementation lower level;

Greg: i am cautious about an XHR-like API which may mislead one to think it is about transport.

Coach: It seems to me that we all agree that we need both kinds of APIs: request/response oriented and messaging oriented. Though XHR replacement needs work...

Greg: i am still cautious about XHR replacement. While I am working on messaging oriented API, i am not sure of XHR oriented API;

Alex: the semantic approach's success depends on convincing developers while XHR approach nees to convince browser vendors.

Jon: what i got for the PortletXHR proposal is that it passes everything to the browser directly. Their ambitions are low.

Coach: Can greg give us a quick overview of his recent work on semantic oriented API?

Greg: i have been doing some implementation of this API. I am hoping to finish the implementation and ready for this conference call, but i am a little late on this. But i am making good progress on this. It supports both pub/sub as well as request/response style communications.

Coach: we have requested Greg to become a committer on the OpenAjax project and Jon is going to work on it;

Jon: congrats Greg.

Coach: so we look forward to seeing Greg's code commit and that will give us a solid basic to have a more indepth discusssion over the next two weeks.

coach: any other busines that we should discuss today?

Coach: Thanks everyone. Talk to you again in two weeks.

Retrieved from "/member/wiki/Communications_Hub_TF_Minutes_2007-01-24"