Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Add lastupdatetimestamp field on fitnessactivity/FitnessActivit ySummary/FitnessActivityFeed

Received: by 10.236.79.225 with SMTP id i61mr4814294yhe.8.1344959105577;
        Tue, 14 Aug 2012 08:45:05 -0700 (PDT)
X-BeenThere: healthgraph@googlegroups.com
Received: by 10.236.113.178 with SMTP id a38ls1143098yhh.9.gmail; Tue, 14 Aug
 2012 08:45:05 -0700 (PDT)
Received: by 10.100.81.4 with SMTP id e4mr1942776anb.26.1344959105066;
        Tue, 14 Aug 2012 08:45:05 -0700 (PDT)
Received: by 10.100.81.4 with SMTP id e4mr1942775anb.26.1344959105044;
        Tue, 14 Aug 2012 08:45:05 -0700 (PDT)
Return-Path: <christopher.barr...@runkeeper.com>
Received: from mail-gg0-f174.google.com (mail-gg0-f174.google.com [209.85.161.174])
        by gmr-mx.google.com with ESMTPS id u67si787141yhi.7.2012.08.14.08.45.05
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 14 Aug 2012 08:45:05 -0700 (PDT)
Received-SPF: pass (google.com: domain of christopher.barr...@runkeeper.com designates 209.85.161.174 as permitted sender) client-ip=209.85.161.174;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of christopher.barr...@runkeeper.com designates 209.85.161.174 as permitted sender) smtp.mail=christopher.barr...@runkeeper.com; dkim=pass header...@runkeeper.com
Received: by ggdk6 with SMTP id k6so651236ggd.5
        for <healthgraph@googlegroups.com>; Tue, 14 Aug 2012 08:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=runkeeper.com; s=google;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=MW5oU2jXrglIIsi3DEgmbzReoLBXwq6SYa1Pz7OSPAA=;
        b=Nehe7yVlNtM243o25gcjH52SHNXTaDt7aj/vcSqtHwFlewDtM4cinTmhRCrGUqTtFb
         5MvE62RVjaAdAUtxVNmE1kWmxb/HCMk93M9YA1QklPH/8f7zadvZH9cFKkEbDkeanjpT
         GY7KCg3nk7HMeJKjbv9LlQZlDhlaVHhvrgxvc=
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:x-gm-message-state;
        bh=MW5oU2jXrglIIsi3DEgmbzReoLBXwq6SYa1Pz7OSPAA=;
        b=aF+ceA4PDNyfuTTOA88PdLdzkfy/i/9BPK8tVmcof/tAmeDncsmfmct2d+K75jF6e2
         JCkItCJPJH0DH2HXDw+jTQ3BeFoGG+9kWVK29vEl39SGhKTheSK1SHXx+jn4NRiZ0exU
         Mjr5VB+ij83CiaV2Y5vPidzsD68pcvtBU/8x17XJq9uBTZ2Nf1D299RiLOsCcK/pIufJ
         fEFYgRBcZPM3H6GleE+r0CMqdctY6GyawGe1MJNcKrwBOGHpnt6+8U97R7fXwlL2MA98
         6eRymzOfq3Ph6LhWqGM3x8kH2xBoaTPVZFNRH49haCppehDKNbCj1SJyKKPe1fecKIqb
         e67A==
Received: by 10.50.34.137 with SMTP id z9mr12616401igi.5.1344959104625; Tue,
 14 Aug 2012 08:45:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.50.110.103 with HTTP; Tue, 14 Aug 2012 08:44:44 -0700 (PDT)
In-Reply-To: <851b219a-293a-44f3-a06e-2ea6bff625d7@googlegroups.com>
References: <6019c59b-0f35-4ed2-ae95-989514e6446b@googlegroups.com> <851b219a-293a-44f3-a06e-2ea6bff625d7@googlegroups.com>
From: Christopher Barratt <christopher.barr...@runkeeper.com>
Date: Tue, 14 Aug 2012 11:44:44 -0400
Message-ID: <CAPFaB4zuZetfYav+X47mAR1hMbRi5F=6ZmK36wTwG-baFG1...@mail.gmail.com>
Subject: Re: Add lastupdatetimestamp field on fitnessactivity/FitnessActivitySummary/FitnessActivityFeed
To: healthgraph@googlegroups.com
Content-Type: multipart/alternative; boundary=14dae93409e5ab2ce004c73bb1b3
X-Gm-Message-State: ALoCoQnVNMIt29Eje6e8wHMbVS7A8usR6fQEeTXSDItw/71e05G7EvodFMOcnLauZC9EpqbWKDMf

--14dae93409e5ab2ce004c73bb1b3
Content-Type: text/plain; charset=UTF-8

Nicola,

Have you taken a look at the modifiedNoEarlierThan parameter on the fitness
feed?

-- Chris

On Tue, Aug 14, 2012 at 3:08 AM, Nicola <supp...@caledos.com> wrote:

> No news means bad news? :-)
> N
>
>
> On Thursday, August 9, 2012 5:52:22 PM UTC+2, Nicola wrote:
>
>> In our app, we keep a copy of all fitness activities so the user can both
>> access to its data offline, and have basic report capabilities on the
>> mobile phone always with him.
>>
>> So, we have the problem of keep up to date informations on the phone.
>> We are setting up a function that every now and then, gets, via
>> FitnessActivityFeed and then via GET single FitnessActivity the activities
>> from the server to check is something is changed.
>>
>> In order to avoid a "brute force" approach (refresh all data!) that is
>> bad for both the client (battery) and your server (bandwidth and workload),
>> I think that if you could add the a "last update timestamp" field at
>> fitnessactivity/**FitnessActivitySummary/**FitnessActivityFeedItem we
>> (and all app that need to keep a copy of your data) could be very efficient
>> in this type of task.
>>
>> Is it possible for you to add it or, is there a different/better approach
>> you can suggest to us?
>> Thanks!
>> Nicola
>>
>

--14dae93409e5ab2ce004c73bb1b3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Nicola,<div><br></div><div>Have you taken a look at the modifiedNoEarlierTh=
an parameter on the fitness feed?</div><div><br></div><div>-- Chris<br><br>=
<div class=3D"gmail_quote">On Tue, Aug 14, 2012 at 3:08 AM, Nicola <span di=
r=3D"ltr">&lt;<a href=3D"mailto:supp...@caledos.com" target=3D"_blank">supp=
o...@caledos.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>No news means bad news? :-)</div><span =
class=3D"HOEnZb"><font color=3D"#888888"><div>N</div></font></span><div cla=
ss=3D"HOEnZb">

<div class=3D"h5"><div>=C2=A0</div><div><br>On Thursday, August 9, 2012 5:5=
2:22 PM UTC+2, Nicola wrote:</div><blockquote style=3D"margin:0px 0px 0px 0=
.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:=
1px;border-left-style:solid" class=3D"gmail_quote">

<div>In our app, we keep a copy of all fitness activities so the user can b=
oth access to its data offline, and have basic report capabilities on the m=
obile phone always with him.</div><div>=C2=A0</div><div>So, we have the pro=
blem of keep up to date informations on the phone. <br>

</div><div>We are setting up a function that every now and then, gets, via =
FitnessActivityFeed and=C2=A0then via GET single FitnessActivity the activi=
ties from the server to check is something is changed. </div><div>=C2=A0</d=
iv><div>

In order to avoid a &quot;brute force&quot; approach (refresh all data!) th=
at is bad for both the client (battery) and your server (bandwidth and work=
load), I think that if you could add the a &quot;last update timestamp&quot=
; field at fitnessactivity/<u></u>FitnessActivitySummary/<u></u>FitnessActi=
vityFeedItem we (and all app that need to keep a copy of your data) could b=
e very efficient in this type of task.</div>

<div>=C2=A0</div><div>Is it possible for you to add it or, is there a diffe=
rent/better approach you can suggest to us?</div><div>Thanks!</div><div>Nic=
ola</div></blockquote></div></div></blockquote></div><br></div>

--14dae93409e5ab2ce004c73bb1b3--