SQS updated

[Ansel Halliburton]

Hello,

Amazon just released a new version of SQS:
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=763

I think the most interesting parts are a new method to get an
approximate count of messages in a queue, and the ability to change a
message's visibility timeout. Also, larger messages are accepted via
the "query" API.

I'll probably take a look at implementing the message count method in
the next week or two.

Ansel

[Mitchell Garnaat]

Hi Ansel -

Unfortunately, they have not made the new functionality available via the REST interface.  How annoying!

I guess the options are to wait and see if they do REST soon, re-implement the SQS interface using Query (could leverage the AWSQueryConnection class used for EC2 and mturk which are also Query-based) or find some way to merge the two together and just implement the new stuff in Query (sounds tricky).

It's not a very complicated interface so it probably wouldn't take that long to redo the whole thing but I find it strange that AWS seems so enamored with this pseudo-REST Query interface, especially after they did such a great REST interface for S3.  Go figure...

Mitch

[mitch]

I just checked in some new SQS code that makes the GetQueueAttributes
and SetQueueAttributes requests available. I decided to stick with
the REST interface (it's just much nicer than the Query) but I also
implemented a QueryConnection that only implements these two
requests. It's all transparent. You can just call q.get_attributes()
and it just handles things for you.

I also have added quite a few docstrings to methods, etc.

Mitch

On May 18, 3:22 pm, "Mitchell Garnaat" <mitch.garn...@gmail.com>
wrote:

> Hi Ansel -
>
> Unfortunately, they have not made the new functionality available via the
> REST interface. How annoying!
>
> I guess the options are to wait and see if they do REST soon, re-implement
> the SQS interface using Query (could leverage the AWSQueryConnection class
> used for EC2 and mturk which are also Query-based) or find some way to merge
> the two together and just implement the new stuff in Query (sounds tricky).
>
> It's not a very complicated interface so it probably wouldn't take that long
> to redo the whole thing but I find it strange that AWS seems so enamored
> with this pseudo-REST Query interface, especially after they did such a
> great REST interface for S3. Go figure...
>
> Mitch
>