Communications Hub TF Minutes 2007-04-11

From MemberWiki

Jump to: navigation, search

Contents

OpenAjax Alliance Communications Hub TF meeting minutes 2007-04-11

Attendees

  • Jon Ferraiolo <jferrai(at)us.ibm.com>
  • Ted Goddard <ted.goddard(at)icesoft.com>
  • Coach Wei <coach(at)nexaweb.com>
  • Ric Smith from Oracle
  • Lounas from SAP
  • Craig from Sun<Craig.McClanahan@Sun.COM>

Agenda

Minutes

  • Scribe: coach
  • Coach did a recap of OpenAjax F2F meeting;
  • Coach: what are the plans going forward?
  • Jon: I recommend we do a plan and high level roadmap first, before we getting into more details of a specicif piece such as client side hub;
  • Coach: I agree. We have done quite a lot of work on the client side; Some work is going on from a protocol perspective; but what about server side?
  • Jon:
    • from the server side perspective, there is a standard messaging convention, like REST. The payload will include some standard wrapper (such as JSON format or XML format). Server side should provide support to process such messaging convention.
  • Ric: Are we talking about payload or REST?
  • Ted: We tried to stay away from payload specification;
  • Jon: but there is wrapper around payload;
  • Ric: We talked about some kind of proxy servlet;
  • Ric: we have to implement special servlet to process byoux;
  • Jon: Greg Wilkin etc at Dojo is trying to make Byoux work with existing servlet technology.
  • Ric: but it would still require servlet implementation to process it. It is probably easy for Java community, but it may not be easy for other communities.
  • Ted: I was thinking of a simpler way than Byoux - only to provide notification service to notify the message availability;
  • Ric: yes, that is also more or less what I am thinking.
  • Coach: Ted, can you write it up as a proposal that we can all look at and discuss?
  • Ted: Ok.
  • Ric: if we stick to pure protocol, and make the suggestion to other communities and see how they respond...
  • Coach: does it mean that Byoux is more than a protocol?
  • Ric: yes. It feels heavier than necessary.
  • Coach: is there any document that summarizes the problems we are trying to solve from the server side?
  • Ric: the short answer is no.
  • Jon: there are lots of materials avaiable in the JavaWorld, for example, supporting comet is difficult.
  • Coach: It is important to define the problems.
  • Jon: Greg summarized some problems;
  • Ric: no, i think it is Joe Walker at DWR. Joe Walker has implemented some similar Pub/Sub structure on the server side and talked about many problems;
  • Coach: Ric, can you reach out to Joe and see if he has any materials that we can use?
  • Ric: sure.
  • Jon: Greg Wilkins implemented a chatting application that is checked into OpenAjax source project, which uses jetty server for doing chatting.
  • coach: I'd propose we focus on creating a problem defintion over the next few weeks;
  • Lunas: I agree.
  • Ted: one approach is to focus on one vs the other first, such as protocol first or server first, etc.

Action Items

  • Ted: create a proposal for a simpler way to address server side communication issues;
  • Ric: to connect with Joe Walker to see whether he has materials around communications related problems etc. and use as feedback to the TF;
  • Coach: to use Ric/Joe and Greg Wilkin's input to create an initial draft of problem definition for discussion.
Retrieved from "/member/wiki/Communications_Hub_TF_Minutes_2007-04-11"