RE: Patches: back-shell abandon is inconsistent (ITS#1792)

[hyc@highlandsun.com]

I think, since the ABANDON request has no reply, the msgid of the Abandon
operation itself is unimportant.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> h.b.furuseth@usit.uio.no
> Sent: Friday, May 03, 2002 1:21 AM
> To: openldap-its@OpenLDAP.org
> Subject: Patches: back-shell abandon is inconsistent (ITS#1792)
>
>
> Full_Name: Hallvard B. Furuseth
> Version: HEAD (2002-05-02)
> OS: Linux
> URL:
> Submission from: (NULL) (158.36.148.34)
>
>
> I made a doc bug which I'm not sure how to deal with, so I'm ITS'ing
> it separately:
>
> The input to all back-shell commands except abandon start with
> 	<OPERATION>
> 	msgid: <message id>
> but the input to abandon starts with
> 	ABANDON
> 	msgid: <message id of operation to abandon>
> and the message id of the abandon operation itself is not present.
>
> There are two possible fixes:  Either document the inconsistency:
> 	http://folk.uio.no/hbf/OpenLDAP/shell-incompat.txt
> or change the calling conventions to shell abandon to
> 	...
> 	msgid: <message id>
> 	...
> 	abandonid: <message id of operation to abandon>
> and send an alert to openldap-announce or openldap-software:
> 	http://folk.uio.no/hbf/OpenLDAP/shell-inconsistent.txt
>
> See also ITS#1784 (back-tcl abandon needs abandoned msgid as argument).
>