<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Technique to modify a timer</title>
    <link>http://www.peertopatent.org/patent/20070260907/activity</link>
    <description>A technique to modify a timer. More particularly, at least one embodiment of the invention relates to a technique to modify a timer value without the timer advancing by a significant amount.</description>
    <language>en-us</language>
    <item>
      <title>Wow, lots of recent comments.  Please note that...</title>
      <category>Technique to modify a timer</category>
      <description>Wow, lots of recent comments.  Please note that while this is good, this pilot is not set up to forward these comments to the USPTO.  According to P2P, only the materials and annotations under the Prior Art section are forwarded to USPTO.  If you know matching prior art, please upload it in that area, and add relevance info for the specific related claims of this application.</description>
      <pubdate>Tue, 19 Feb 2008 11:36:40 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>Doh!  When I logged into P2P, it switched me fr...</title>
      <category>Technique to modify a timer</category>
      <description>Doh!  When I logged into P2P, it switched me from one application to another.  The above is true, but not intended to be posted here. 
</description>
      <pubdate>Tue, 19 Feb 2008 11:37:39 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>I think Claim 2 is more wishful thinking than i...</title>
      <category>Technique to modify a timer</category>
      <description>I think Claim 2 is more wishful thinking than invention. The claim is to update a machine-readable timer in one micro-operation -- and I would go so far as to say such an invention would be a really great thing -- but we are not told how to do that.  There should be logic diagrams or circuits showing how a person schooled in the art of setting machine-readable timers would use this invention to update a timer using a single micro-operation.  

Saying that single micro-operation would be faster than multiple micro-operations is not an invention.  Showing us how to build a single micro-operation timer updater might be.

I don't have any prior art to give you, but the guys that build atomic clocks must have thought about this problem on a far deeper level than I have.  The National Institute of Standards and Technology should be able to help.</description>
      <pubdate>Tue, 19 Feb 2008 07:59:32 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>Claim 1 is too broad and generic; almost any ti...</title>
      <category>Technique to modify a timer</category>
      <description>Claim 1 is too broad and generic; almost any timer performs the steps discosed in claim 1, so they make the subject-matter of claim 1 not new.
The compensation of the elapsed time (claim 3) is essential to solve the problem posed by the invention so it must be added to claim 1.  </description>
      <pubdate>Fri, 28 Dec 2007 03:08:25 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>Upon closer examination it appears to me that t...</title>
      <category>Technique to modify a timer</category>
      <description>Upon closer examination it appears to me that the distinction the application draws between its [[claim 1]] and the prior art (as described even in the application itself) is the use of *an* (a single) instruction to trigger the updating steps.  According to the application, this saves time compared to prior art in which multiple instructions are required to effect the timer update.  However, the wording of [[claim 1]] does not specifically require the updating method itself to comprise a single machine instruction.  The claim thus appears broader than the description suggests, and as a result, a somewhat bigger target for prior art relevance.  For example, a single branch or jump instruction could cause a machine to execute a multi-instruction timer update method (subroutine).  Thus, one may not need to find prior art that performs the updating steps all within one machine instruction.</description>
      <pubdate>Fri, 07 Dec 2007 19:39:37 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>Perhaps this is where [[claim 2]] is supposed t...</title>
      <category>Technique to modify a timer</category>
      <description>Perhaps this is where [[claim 2]] is supposed to come in.  Its language appears to try to limit the updating to a single instruction; however, I think that may also fail to do so.  [[claim 2]] says that the steps are &amp;quot;performed in response to...only one micro-operation&amp;quot;.  Extending my argument above concerning [[claim 1]], I don't think that &amp;quot;performed in response to&amp;quot; clearly enough requires this all to be part of the execution of a single machine instruction, and again propose that the single micro-operation that the update is responsive to might in prior art be a branch or jump instruction.  I would find the claim more consistent with its apparent intent if it said something like &amp;quot;wherein the reading, updating, and storing comprise the execution of only one micro-operation&amp;quot;.</description>
      <pubdate>Fri, 07 Dec 2007 19:57:23 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>The independent claims here appear to be very g...</title>
      <category>Technique to modify a timer</category>
      <description>The independent claims here appear to be very generic in nature; surely existing processors must already perform the steps listed therein when updating clocks/timers.  I assume the potential novelty is in the inclusion of a compensating amount in the new timer value calculation, to account for any new delay introduced by the updating operation itself.  This is reflected in [[claim 3]] for example, and those deriving from it, but not in [[claim 1]].  I'm not certain what exactly [[claim 2]] is after, but it doesn't sound to this relative layman to be necessarily connected to the compensation mechanism and could be existing art as well.  [[claim 4]] also sounds quite generic to me.</description>
      <pubdate>Sun, 25 Nov 2007 17:26:30 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>The notion of compensating for the elapsed time...</title>
      <category>Technique to modify a timer</category>
      <description>The notion of compensating for the elapsed time is included in a more complicated timer update scenario in US6,591,370,&amp;quot; Multinode computer system with distributed clock synchronization system&amp;quot;</description>
      <pubdate>Thu, 06 Dec 2007 14:42:46 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
    <item>
      <title>Indeed, that does look quite relevant for at le...</title>
      <category>Technique to modify a timer</category>
      <description>Indeed, that does look quite relevant for at least [[claim 3]].  Please enter that patent in the Prior Art section for this application.</description>
      <pubdate>Fri, 07 Dec 2007 19:49:30 -0800</pubdate>
      <guid>http://www.peertopatent.org/patent/20070260907/discussion</guid>
    </item>
  </channel>
</rss>
