Re: [rtcweb] Proposed text for local recording use case

Dzonatas Sol <dzonatas@gmail.com> Wed, 24 August 2011 00:58 UTC

Return-Path: <dzonatas@gmail.com>
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 DE52321F8564 for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 17:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.165
X-Spam-Level:
X-Spam-Status: No, score=-4.165 tagged_above=-999 required=5 tests=[AWL=-0.566, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 bm2x3CVrFMXF for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 17:58:19 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id EB89021F8556 for <rtcweb@ietf.org>; Tue, 23 Aug 2011 17:58:18 -0700 (PDT)
Received: by yie12 with SMTP id 12so641788yie.31 for <rtcweb@ietf.org>; Tue, 23 Aug 2011 17:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qyCZsMRDKw4kiqH1YiO+aIexvaFI6c1BI81dCpL54FA=; b=HFVeU9Qr3euVWE4b03uVDZQcnfQC1xvSnQWMgmBMfkpVpZ5dLvSvnyFpBy6PxyrljU 5dOblnbxmFW4PQBklzDyqAihdGd+OJfyhqhrpQVPMOq7NG54DGBhoMOCqAsPPTWx/+KV GP3QF2qT+lKjBr9Mt3oMxtgnO0jJmazvYK2ew=
Received: by 10.146.27.25 with SMTP id a25mr4366865yaa.38.1314147566871; Tue, 23 Aug 2011 17:59:26 -0700 (PDT)
Received: from [192.168.0.50] (adsl-70-133-70-225.dsl.scrm01.sbcglobal.net [70.133.70.225]) by mx.google.com with ESMTPS id f48sm761128yhh.0.2011.08.23.17.59.25 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 23 Aug 2011 17:59:26 -0700 (PDT)
Message-ID: <4E544D41.5060801@gmail.com>
Date: Tue, 23 Aug 2011 18:00:49 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <A444A0F8084434499206E78C106220CA0B00FDAE6A@MCHP058A.global-ad.net> <5AF1B737-690C-48DE-A654-12E44A9644DD@cisco.com>
In-Reply-To: <5AF1B737-690C-48DE-A654-12E44A9644DD@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Proposed text for local recording use case
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 00:58:20 -0000

Native Client mode needs Native Server mode as different accounts local 
and remote; like, six hours worth of samples from physical grid 
simulation; scene data driven graphs store optional.

Geolocation schema for C.A.V.E.s was one of many common questions never 
made FAQ.

On 08/23/2011 02:56 PM, Cullen Jennings wrote:
> On Aug 22, 2011, at 8:42 AM, Elwell, John wrote:
>
>    
>> 4.2.xx Local Session Recording
>> In this use case, the web application user wishes to record a real-time communication locally, such that transmitted and received audio, video or other real-time media are stored in one or more files. For a given medium, the two directions of transmission can be stored in the same file (mixed) or in separate files. The web application also stores metadata that gives context to the stored media.
>>
>> New requirements:
>> Fxx1: The browser MUST be able to store transmitted and received media in local files.
>>
>> Axx1: The web application MUST be able to ask the browser to store transmitted and received media in local files, and in the case of audio at least, ask for the two directions of transmission to be stored mixed or separately.
>>
>> John
>>      
> I think I want something just slightly different and that is to send media that is data in the JS and to be able to hand media as data to the JS. If the JS happens to read / write that to a file that is fine with me but this allows the JS to operate on the data or synthetically generate media and opens the doors to the possibility of writing a codec in JS or NACL.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>    


-- 
--- http://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering
Ag-Biotech, Virtual Reality, Consultant