Re: Compound requests

New Message	Reply	About this list	Date view	Thread view	Subject view	Author view	Attachment view

From: Brent Callaghan (Brent.Callaghan@eng.sun.com)
Date: 06/08/99-11:22:18 AM Z

Next message: Mike Eisler: "Re: Extended attributes"
Previous message: Mike Eisler: "Re: Compound requests"
Maybe in reply to: Noveck, Dave: "Compound requests"

Date: Tue, 8 Jun 1999 09:22:18 -0700 (PDT)
From: Brent Callaghan <Brent.Callaghan@eng.sun.com>
Message-Id: <199906081622.JAA01156@terra.eng.sun.com>
Subject: Re: Compound requests

Dave Noveck writes:
> In the definition of COMPOUND4args and COMPOUND4resok
> there is something called tag which is a utf8string.
> There is no explanation in the text (that I can find)
> about what this is supposed to be used/intended for.

The tag is intended to be a short, descriptive string
intended for display by packet sniffers like tcpdump
or snoop - or other diagnostic software.

These programs could display an abbreviated sequence of operations
in the compound op, e.g.

	PUTFH 0x5h33 LOOKUP "thing" NVERIFY 0x60 READ 0 8192 

but the availability of a tag string would make the particular
request easier to recognize, e.g. 

	"Cache Check" : PUTFH 0x5h33 LOOKUP "thing" .....

Yes, the tag needs more description in the spec.

	Thanks
		Brent

Next message: Mike Eisler: "Re: Extended attributes"
Previous message: Mike Eisler: "Re: Compound requests"
Maybe in reply to: Noveck, Dave: "Compound requests"

New Message	Reply	About this list	Date view	Thread view	Subject view	Author view	Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:47:11 AM Z CST