openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #05173
Re: Push vs Polling (from Versioning Thread)
On Oct 28, 2011, at 10:33 AM, George Reese wrote:
> You are describing an all-purpose system, not one that supports the narrow needs of IaaS state notifications.
>
> There's no reason in this scenario to guarantee message delivery.
Like I said, there are a lot of factors to consider. And guarantee delivery may or may not be a requirement based on your use case. For example, wouldn't we want to monitor based on state changes? Missing a message could mean not sending an alert, right? How do you compensate for that if you don't guarantee delivery?
References
-
API Versioning and Extensibility
From: Mark Nottingham, 2011-10-25
-
Re: API Versioning and Extensibility
From: Bryan Taylor, 2011-10-26
-
Re: API Versioning and Extensibility
From: Jorge Williams, 2011-10-26
-
Re: API Versioning and Extensibility
From: Bryan Taylor, 2011-10-27
-
Re: API Versioning and Extensibility
From: Jorge Williams, 2011-10-27
-
Re: API Versioning and Extensibility
From: George Reese, 2011-10-27
-
Re: API Versioning and Extensibility
From: Jorge Williams, 2011-10-27
-
Re: API Versioning and Extensibility
From: George Reese, 2011-10-27
-
Push vs Polling (from Versioning Thread)
From: Bryan Taylor, 2011-10-27
-
Re: Push vs Polling (from Versioning Thread)
From: George Reese, 2011-10-27
-
Re: Push vs Polling (from Versioning Thread)
From: Monsyne Dragon, 2011-10-27
-
Re: Push vs Polling (from Versioning Thread)
From: Bryan Taylor, 2011-10-28
-
Re: Push vs Polling (from Versioning Thread)
From: George Reese, 2011-10-28
-
Re: Push vs Polling (from Versioning Thread)
From: Jorge Williams, 2011-10-28
-
Re: Push vs Polling (from Versioning Thread)
From: George Reese, 2011-10-28
