27.0.0.1', 'REQUEST_METHOD': 'GET', 'SERVER_NAME':
'localhost', 'SERVER_PORT': '8094', 'SERVER_PROTOCOL': 'HTTP/1.0',
'SERVER_SOFTWARE': 'Development/1.0'})
2242 infile,
2243
r update.) Frankly,
> I'm surprised that 5 times/second is too fast. (5x/second is 200ms per
> update.)
>
> On Aug 10, 5:24 am, "Nick Johnson (Google)"
> wrote:
>
> > On Sun, Aug 9, 2009 at 4:58 PM, Markitecht wrote:
>
> > > Thanks Nick, makes comple
ntion.
best,
Christopher
On Aug 7, 6:02 am, "Nick Johnson (Google)"
wrote:
> Hi Markitecht,
>
> It sounds like your best option is to have a single Interaction entity
> for each unique string. You can use the key name to ensure uniqueness.
> Then, to record a new interacti
I am writing a dirt-simple tracking API.
For the sake of explanation, i will over-simplify my question even
further.
I have an endpoint that accepts one item of string metadata, and saves
a new instance of an Interaction object.
(the interaction object also saves the user and the date created)
