Sticky-ness and API errors

5 views
Skip to first unread message

Pedro Melo

unread,
Oct 3, 2010, 11:18:31 AM10/3/10
to noti...@googlegroups.com
Hi,

I'm finishing up a Perl module for the NotifyIO API and I have two questions:

First one is about sticky. According to
http://groups.google.com/group/notify-io/web/developers, the sticky
argument is deprecated, and we should just add a tag sticky if we want
it.

I tried that but the NotifyIO Desktop does not honor the sticky tag,
but does honor the sticky parameter. So I assume that the deprecation
is false, and we should keep on using the sticky argument. Correct?

Also, I'm sending notifications just fine now, but the API answer is
something like this:

HTTP/1.1 200 OK
Connection: close
Date: Sun, 03 Oct 2010 15:13:45 GMT
Server: TwistedWeb/10.1.0
Content-Type: text/html
Client-Date: Sun, 03 Oct 2010 15:13:46 GMT
Client-Peer: 174.143.203.167:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked

[Failure instance: Traceback: <type 'exceptions.KeyError'>:
'578638b6c9072d621bc62c28d3ce60be34e13592'
/usr/local/lib/python2.6/dist-packages/twisted/web/client.py:175:handleResponse
/usr/local/lib/python2.6/dist-packages/twisted/web/client.py:340:page
/usr/local/lib/python2.6/dist-packages/twisted/internet/defer.py:318:callback
/usr/local/lib/python2.6/dist-packages/twisted/internet/defer.py:424:_startRunCallbacks
--- <exception caught here> ---
/usr/local/lib/python2.6/dist-packages/twisted/internet/defer.py:441:_runCallbacks
api/server.py:126:notify_success
]

As I said, I'm getting the notifications that I'm posting, but I also
get that traceback.

Bye,
--
Pedro Melo
http://www.simplicidade.org/
xmpp:me...@simplicidade.org
mailto:me...@simplicidade.org

Jeff Lindsay

unread,
Oct 6, 2010, 2:55:06 PM10/6/10
to noti...@googlegroups.com
I remember somebody was working on a patch to honor the sticky tag, but I think it went MIA. We can honor it (apply sticky flag) in the meantime on the server. You might want to add a ticket for that here: http://gliderlab.lighthouseapp.com/projects/55825-notifyio/tickets

-jeff
--
Jeff Lindsay
http://progrium.com

Jeff Lindsay

unread,
Oct 7, 2010, 3:17:45 AM10/7/10
to noti...@googlegroups.com
Also, I fixed this error.

On Sun, Oct 3, 2010 at 8:18 AM, Pedro Melo <me...@simplicidade.org> wrote:

Pedro Melo

unread,
Oct 7, 2010, 11:06:33 AM10/7/10
to noti...@googlegroups.com
Hi,

On Thu, Oct 7, 2010 at 8:17 AM, Jeff Lindsay <prog...@gmail.com> wrote:
> Also, I fixed this error.

So should we still use sticky or should we tag with "sticky" now?

Jeff Lindsay

unread,
Oct 7, 2010, 2:48:09 PM10/7/10
to noti...@googlegroups.com
Sorry, I wasn't clear. I fixed the error that comes up when sending notifications (but doesn't actually affect sending them). As for sticky, I'd keep using sticky until we get a patch in. We'll make sure to be backwards compatible afterwards.

Pedro Melo

unread,
Oct 8, 2010, 1:36:02 AM10/8/10
to noti...@googlegroups.com
Hi

On Thu, Oct 7, 2010 at 7:48 PM, Jeff Lindsay <prog...@gmail.com> wrote:
> Sorry, I wasn't clear. I fixed the error that comes up when sending
> notifications (but doesn't actually affect sending them). As for sticky, I'd
> keep using sticky until we get a patch in. We'll make sure to be backwards
> compatible afterwards.

Ok, cool.

Reply all
Reply to author
Forward
0 new messages