inline BB (was Re: do you know enough about what (other) Bazaar developers are doing?)

[John Arbash Meinel]

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

Daniel Watkins wrote:
| On Thu, 7 Aug 2008 10:39:37 +1000
| "Martin Pool" <mbp at canonical.com> wrote:
|> Of course there may be some delay before you realize your message is
|> delayed, but I think if you're in a hurry you'll be pinging someone
|> for a review and they'll notice, and if you're not in a hurry you can
|> notice tomorrow.
| It might be worth having an XMLRPC interface.  If PQM is anything to go
| by, it'll end up being desirable anyway so doing it now seems to make
| sense (to me, at least).
|

Actually, in this is case email might actually be better. Because if BB
accepts your request through XML-RPC, and then crashes, it may be lost.
While if you use email, it will either be in BB's inbox, or SMTP server
ahead of it will be holding it waiting to retransmit.

Certainly BB could be structured correctly (not give an ok, until the
message is written to a queue that won't be flushed until the message
has been safely passed on.)

My bigger concern is that right now when BB goes down, it becomes hard
to review stuff because we rely on it to track things for us to do. It
is still *possible* though, because the real discussion is all in our
email clients. If BB was the gateway, then we may not even have the
email yet.

I certainly would expect to have a serial+parallel BB scanner. So that
if someone sends direct to the list, BB notices, and if you send
directly to BB it would then send it on with the attached url.

I *like* BB a lot, but it hasn't traditionally shown the same uptime
that email has. (Though I don't believe it has ever *lost* anything.
Though maybe it is just Aaron's diligence to send things through again
when he needs to.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiaUIUACgkQJdeBCYSNAAPjDQCeMtoKYkl7cziqRrnESweiVsb6
wVwAoNI0w5a6IK3yz7jpVA3dIh2EFKHy
=SJ1v
-----END PGP SIGNATURE-----