[sldev] Re: Inventory Loss due to capped IM's

[Sean Lynch]

A couple of us have been investigating RabbitMQ (Erlang implementation of
AMQP) for a couple of applications, and this seems like a potential
application for it, along with moving offline IMs completely out of the
database. You send a transactional, persistent message with the inventory
offer, which would fail if the queue was full or it otherwise couldn't be
placed in the recipient's queue. It would then sit there until the reipient
accepted or declined it or some interval had passed, after which it would be
returned to the sender's lost and found named something along the lines of
"declined/expired inventory offer to X: <original name>".

Just a thought. I haven't actually discussed this with anyone :) Note that
we don't have RabbitMQ in production anywhere yet, and we don't even know if
RabbitMQ or AMQP will work for any of our purposes.

On Sun, May 18, 2008 at 2:01 AM, Robin Cornelius <robin.cornelius at gmail.com>
wrote:

> > Robin -
> >=20
> > these are all great ideas. i especially like the idea of having separat=
> e
> > queues for IMs and object-offers - it could directly improve our conten=
> t
> > loss problem, which has been a high priority for us lately.   if there
> > isn't already such a proposal in JIRA, you should create one.
> >=20
> >
>
> I've found some similar issues and some that talk around this exact
> point but not one that exactly says this (often they are talked about in
> the comments and is not the focus of the JIRA) and they all seem to be
> marked as VWR bugs too so i've created :-
>
> SVC-2364
>
> Robin
>
>
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20080518/c52f861f/attachment-0001.htm