[Pulp-list] Messaging Questions

[Jason Dobies]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've been thinking about some of the edge cases we need to address in
messaging. These may be addressed already, I just wanted to how we're
handling things.


- - What happens if a message is put on the queue for an agent, but the
agent never comes online to pick it up? Do they expire? We'll need some
sort of reaper to time out the request in the server database so it
doesn't perpetually look like it's in progress.

- - What happens if an agent picks up a message but never replies? Same
thing here, we'll need a reaper to mark requests as timed out or in this
case, that the agent never replied.

- - Is there anything in the reply that validates that it came from the
correct agent? For instance, I send package install request 1234 to
agent A, but agent B for some reason replies that 1234 was completed.

- - This one affects just about all of the previous: what happens if a
consumer re-registers? Will it reuse the same queue as it previously
did? If not, when does that queue get deleted? What happens if that
re-registration happens while the agent is doing a task before it
replies, will it confuse the server that the reply came from a
"different" consumer?

- - Are replies back to the server guaranteed delivery as well? I'm
thinking of the situation where the server is offline when the agent
finishes doing its business.



- -- 
Jason Dobies
RHCE# 805008743336126
Freenode: jdob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMLeUqAAoJEOMmcTqOSQHCxBwH/1WQxzUAtGJqA1IlbC26ZWaj
zl7+lCcoVuvr3OKhWFmtZ2oFCBg76xdILgP0xPWq/whrDmNeqGUW+SXsxGheC+Zs
eoLoWYcmkAwz3tLKuq6C9U8DT+fkpC+/9FEIJDFvNlojF0CiuBd/K2XqySEUhjK5
Hh9Pfg8JuavbE6TNrmscHRu9qpv1VEIPq1IUsqXvfd5c0ACqNBQuCwfjGVROgKb7
aqzo2g26+oDEV3NDwbIuZ7I9esOuMBlSCvoEJLWvQN1Mzrmeu71zRYrrIOzLKVff
/KL0L+95hMQbi8p04ySqkmLzCNR+XqKA5VWWyKhq3TNEAZe+C6Mi4qHVyCU06yU=
=W6kO
-----END PGP SIGNATURE-----