| bio | website | hewgill.com |
|---|---|---|
| location | Auckland, New Zealand | |
| age | 43 | |
| visits | member for | 3 years, 1 month |
| seen | Jun 12 at 19:48 | |
| stats | profile views | 56 |
Software geek.
Twitter: @ghewgill
|
Aug 19 |
revised |
Stack Overflow ebooks for Kindle version 2012.08 |
|
Aug 7 |
awarded | Nice Question |
|
May 22 |
accepted | Why does the /events service sometimes pause for a couple of minutes? |
|
May 20 |
awarded | Yearling |
|
May 11 |
awarded | Tumbleweed |
|
May 10 |
awarded | Popular Question |
|
May 7 |
comment |
SENotifier, a Stack Exchange inbox notifier for Mac OS X @PaulPeelen: That's curious. Thanks for the info, I'll see if I can find out why that is happening. |
|
May 7 |
comment |
SENotifier, a Stack Exchange inbox notifier for Mac OS X @PaulPeelen: Do you have the Growl application installed? If so, which version? |
|
May 7 |
comment |
SENotifier, a Stack Exchange inbox notifier for Mac OS X @PaulPeelen: Is it possible that you have two instances of the notifier running at the same time? This can happen accidentally if you ask it to hide itself, then start another one. |
|
May 4 |
revised |
StackHose: live real-time event stream in your browser deleted 4 characters in body |
|
May 4 |
revised |
StackHose: live real-time event stream in your browser added 9 characters in body |
|
May 4 |
revised |
StackHose: live real-time event stream in your browser deleted 51 characters in body |
|
May 4 |
asked | StackHose: live real-time event stream in your browser |
|
May 4 |
revised |
Firehose JSON streaming event service added 10 characters in body |
|
Apr 29 |
revised |
Firehose JSON streaming event service added 3 characters in body |
|
Apr 27 |
answered | Add message ID to inbox items |
|
Apr 27 |
comment |
SENotifier, a Stack Exchange inbox notifier for Mac OS X Thanks! The red message is a warning message, so it probably doesn't matter much. But I'll see if I can find a way to change that. |
|
Apr 24 |
revised |
Firehose JSON streaming event service edited tags |
|
Apr 20 |
comment |
Why does the /events service sometimes pause for a couple of minutes? @russau: I think you're on to something. I tried adding a random nonce= parameter to the query, but that didn't seem to help. Then I tried decreasing the since= parameter by 1 every time I got no results, and that does seem to avoid this problem (and I now get individual periods with no new events). |
|
Apr 20 |
comment |
Why does the /events service sometimes pause for a couple of minutes? @russau: That's a good point. If the caching is done at a layer above the API request handler, and during some 10-second period there is no new activity, then subsequent requests will use the same since field. That would explain why I never see single 10-second periods with 0 new events. |