WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [RFC] PVFB: Add refresh period to XenStore parameters?

To: Markus Armbruster <armbru@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC] PVFB: Add refresh period to XenStore parameters?
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Tue, 6 May 2008 18:29:59 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 May 2008 10:30:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <87lk2ntm0z.fsf@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <20080304161220.GA9852@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080501175536.GV4797@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080502160638.GG4819@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <877ie917ix.fsf@xxxxxxxxxxxxxxxxx> <20080505091808.GC4497@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87ej8hysv6.fsf@xxxxxxxxxxxxxxxxx> <20080505165008.GP4497@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87ve1rv8xb.fsf@xxxxxxxxxxxxxxxxx> <20080506163255.GP4430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87lk2ntm0z.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Markus Armbruster, le Tue 06 May 2008 18:50:04 +0200, a écrit :
> > Instead of expressing idleness or "status", maybe we could rather
> > express whether periodic update notifications are wanted or not, and let
> > the backend request an explicit update notification when it feels the
> > need for one (low-frequency thumbnail update). It has the advantage of
> > only talking about the PVFB protocol itself and not something around it
> > (idleness of the actual output).  That is also backward compatible in
> > that a frontend which doesn't know these two events will just continue
> > sending periodic update notifications, which is fine for the backend.
> 
> I think that's a better way to define this feature.

More precisely, we could have an UPDATE_PERIOD event which carries
an advice from the backend about how often the frontend should sent
update notifications (0 if periodic notification is not useful), and a
REQUEST_UPDATE event that requests a one-time update notification?  The
latter could even contain the requested area? (not sure whether it'd be
really useful considering the added complexity, though).

Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>