Received: by 10.216.135.82 with SMTP id t60mr1391896wei.1.1335963943741;
        Wed, 02 May 2012 06:05:43 -0700 (PDT)
X-BeenThere: api-craft@googlegroups.com
Received: by 10.180.105.5 with SMTP id gi5ls586655wib.3.gmail; Wed, 02 May
 2012 06:05:31 -0700 (PDT)
Received: by 10.180.90.198 with SMTP id by6mr877583wib.4.1335963931277;
        Wed, 02 May 2012 06:05:31 -0700 (PDT)
Received: by 10.180.90.198 with SMTP id by6mr877582wib.4.1335963931265;
        Wed, 02 May 2012 06:05:31 -0700 (PDT)
Return-Path: <stev...@gmail.com>
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169])
        by gmr-mx.google.com with ESMTPS id n1si7153722wiy.0.2012.05.02.06.05.31
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 02 May 2012 06:05:31 -0700 (PDT)
Received-SPF: pass (google.com: domain of stev...@gmail.com designates 209.85.212.169 as permitted sender) client-ip=209.85.212.169;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of stev...@gmail.com designates 209.85.212.169 as permitted sender) smtp.mail=stev...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-wi0-f169.google.com with SMTP id hm17so4214518wib.2
        for <api-craft@googlegroups.com>; Wed, 02 May 2012 06:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=slYWpw/ecjRwbpuXlP6X8iF5ERAdeIIWqp3HuORUBP8=;
        b=ZZc49aL1st9x8wycfliJMRpUeObsjfZD25xMZlOkrZqfo2U4JXATsZUudo1Tntfqak
         /BbH7rzn+Ktj1aHxxf6mjQ0oCqHGVDej+LuNzzDucBjNIZXdhhy/4MTXo++AgBQaf7I9
         J7+SUUQCNMlbGCMU+zxyUr21LVcU9jnIN9xNCDO87k4Nc3QMP2ql9vQoq1lguihyGRRf
         jWf6NlNcT8c8gHANWhP8bBoIs0tK6Qt7ufI+xj455HWwuPtPu9s5vLNTnnl00R14fMTd
         sLSMZdBJkm0Bhb65ojny/nGESzLeY44ceaDkaPzYjTEsBSFkqfwIT4qXXVMLQHsGpjf2
         hp1Q==
Received: by 10.216.131.206 with SMTP id m56mr16448472wei.92.1335963930565;
        Wed, 02 May 2012 06:05:30 -0700 (PDT)
Return-Path: <stev...@gmail.com>
Received: from [192.168.1.63] (245.Red-79-158-51.staticIP.rima-tde.net. [79.158.51.245])
        by mx.google.com with ESMTPS id ca3sm44109425wib.6.2012.05.02.06.05.28
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 02 May 2012 06:05:29 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: Application 'Player'
From: Steven WIllmott <stev...@gmail.com>
In-Reply-To: <26681563.751.1335957442090.JavaMail.geo-discussion-forums@pbfr5>
Date: Wed, 2 May 2012 15:05:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF8B95B6-06F0-451D-A672-A5423BCAA...@gmail.com>
References: <26681563.751.1335957442090.JavaMail.geo-discussion-forums@pbfr5>
To: api-craft@googlegroups.com
X-Mailer: Apple Mail (2.1257)


Useful way of thinking about this. In a way today's "application player" =
is the web browser (renders content, renders controls like next, create, =
destroy, auth, =85) but it's both too complex (in some contexts you have =
a lot of controls you don't need) and too limited (you can can't create =
a custom enough interface to "play" some applications) and you can't =
interact (well) with native resources.

On May 2, 2012, at 1:17 PM, landlessness wrote:
> Powerful metaphor for client side of HATEOAS:
>=20
> Application 'Player'
> =
http://vikasjee.wordpress.com/2012/04/30/where-is-my-application-player/