From owner-cvs-all  Tue Apr 16 12:13:17 2002
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 33C3D37B428; Tue, 16 Apr 2002 12:12:46 -0700 (PDT)
Received: (from sobomax@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g3GJCk118135;
	Tue, 16 Apr 2002 12:12:46 -0700 (PDT)
	(envelope-from sobomax)
Message-Id: <200204161912.g3GJCk118135@freefall.freebsd.org>
From: Maxim Sobolev <sobomax@FreeBSD.org>
Date: Tue, 16 Apr 2002 12:12:46 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: projects/mfcns/handler MFCns_handler.py
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

sobomax     2002/04/16 12:12:46 PDT

  Modified files:
    mfcns/handler        MFCns_handler.py 
  Log:
  Attempt to fix ordering issues when sending MFC notification - seemingly
  notifications are coming out in LIFO order instead of FIFO. Investigation
  revealed that the service does it right, but apparently after they have
  beed sent by the service notifications are gathered in some queue, from
  which they are coming in the LIFO order. Try to workarond the problem
  by introducing artifical delay between sending each subsequent notification
  (10 seconds).
  
  Reported by:    rwarson
  
  Revision  Changes    Path
  1.16      +7 -0      projects/mfcns/handler/MFCns_handler.py

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message