Using typica sqs2 package instead of sqs

[shlomo....@gmail.com]

Hi,

Lifeguard uses the "older" API version of SQS via typica's
com.xerox.amazonws.sqs pacakge.

I have a number of queues created using the newer API version that I
want to use via lifeguard.

Is there any way to configure lifeguard to use the newer API version
in com.xerox.amazonws.sqs2 ?

Thanks.

.. Shlomo

[David Kavanagh]

Yes and no. It's pretty easy to switch over to the new APIs except
that lifeguard uses an API which sets message visibility. That feature
is not in the new version of SQS. I've heard they are working on it
(along with queue sharing), so I've just been holding off on the
switch so that lifeguard functionality is not impacted.

David

[shlomo]

I see that lifeguard uses the old API to extend the message's
visibility lock until the service completes. This is the functionality
that is not available in the new API.

I'm looking for a workaround so I can use the new API. The major
advantage of the new API is that using it is 1000 times less expensive
than the old one.

Maybe requiring services to be "interruptible" ? That is, do not rely
on extending the message visibility - instead, use the queue-standard
visibility timeout. If this visibility times out then we notify the
Service's thread that it should give up. Then, it would be up to the
queue owner to make sure that its default message visibility timeout
is long enough to allow the longest-running request to be processed.
Might this work?

.. Shlomo

On Aug 15, 3:08 pm, "David Kavanagh" <dkavan...@gmail.com> wrote:
> Yes and no. It's pretty easy to switch over to the new APIs except
> that lifeguard uses an API which sets message visibility. That feature
> is not in the new version of SQS. I've heard they are working on it
> (along with queue sharing), so I've just been holding off on the
> switch so that lifeguard functionality is not impacted.
>
> David
>