Return-Path: X-Original-To: rtcweb@ietfa.amsl.com Delivered-To: rtcweb@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFADB21F8B90 for ; Thu, 15 Sep 2011 23:29:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.233 X-Spam-Level: X-Spam-Status: No, score=-2.233 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwSjLUNr++vG for ; Thu, 15 Sep 2011 23:29:46 -0700 (PDT) Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id 2AC3221F8B8C for ; Thu, 15 Sep 2011 23:29:46 -0700 (PDT) Received: from [192.168.40.24] (ns.webway.se [87.96.134.125]) by smtp7.webway.se (Postfix) with ESMTPA id D1C1F754BCE4 for ; Fri, 16 Sep 2011 06:31:56 +0000 (UTC) From: "Olle E. Johansson" Content-Type: multipart/alternative; boundary="Apple-Mail=_475369E4-7522-45D2-AF56-03AC7BB64406" Date: Fri, 16 Sep 2011 08:32:34 +0200 Message-Id: <1C8B5EFA-2205-4B67-A800-4961FD6B116C@edvina.net> To: rtcweb@ietf.org Mime-Version: 1.0 (Apple Message framework v1244.3) X-Mailer: Apple Mail (2.1244.3) Subject: [rtcweb] Data transfer X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2011 06:29:46 -0000 --Apple-Mail=_475369E4-7522-45D2-AF56-03AC7BB64406 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii A comment on the list made me go back and re-read the charter. One thing = I had missed is the data transfer part of rtcweb. "The goal is to enable innovation on top of a set of basic components. One core component is to enable real-time media like audio and video, a second is to enable data transfer directly between clients." Most of the discussions on the list has been about the media. What are = the ideas for data transfer? Applications? To me, this seems like an interesting feature. If it's a plain data = transfer session, a bidirectional session, it's a way to open a session = from Javascript to any server, acting as an rtcweb client, which is = different from the current sandbox model. I could have missed this = discussion, but if not, I think this is an interesting topic to bring = up. Another note, which I think is purely a mistake, is to forget realtime = text - T.140 and just state audio and video. The T.140 users are natural = early adoptor users of rtcweb. /O= --Apple-Mail=_475369E4-7522-45D2-AF56-03AC7BB64406 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii A = comment on the list made me go back and re-read the charter. One thing I = had missed is the data transfer part of rtcweb.

"The goal is to enable innovation = on
  top of a set of basic components.  One core component is =
to enable
  real-time media like audio and video, a second is to enable data
  transfer directly between clients."
Most of the discussions on = the list has been about the media. What are the ideas for data transfer? = Applications?

To me, this = seems like an interesting feature. If it's a plain data transfer = session, a bidirectional session, it's a way to open a session from = Javascript to any server, acting as an rtcweb client, which is different = from the current sandbox model. I could have missed this discussion, but = if not, I think this is an interesting topic to bring = up.

Another note, which I think is purely a = mistake, is to forget realtime text - T.140 and just state audio and = video. The T.140 users are natural early adoptor users of = rtcweb.

/O
= --Apple-Mail=_475369E4-7522-45D2-AF56-03AC7BB64406--