SourceForge : artf2624: (1667) Why is there an offset in the Streamable seekRead / seekWrite?

Project: OGSA-ByteIO-WG Trackers > ByteIO Specification > View Artifact

Artifact artf2624 : (1667) Why is there an offset in the Streamable seekRead / seekWrite?

Tracker:	ByteIO Specification
Title:	(1667) Why is there an offset in the Streamable seekRead / seekWrite?
Description:	ISSUE: Why is there an offset in the Streamable seekRead / seekWrite? DISCUSSION: This is fine (and useful) for implementations where such an offset can be provided. Where implementations cannot provide an offsetable read/write, an appropriate fault should be returned. SOLUTION: Check consistency with listed faults and determine if fault is required .
Submitted By:	Neil Chue Hong
Submitted On:	10/18/2005 11:32 AM EST
Last Modified:	10/28/2005 7:09 AM EST
Closed:	10/28/2005 7:09 AM EST

	Status / Comments		Change Log		Associations		Attachments

Status
Group: *
Status:*	Closed
Category: *
Customer: *
Priority: *	0
Assigned To: *	Mark Morgan
Reported in Release: *
Fixed in Release: *
Estimated Hours: *	0
Actual Hours: *	0

Comments

Neil Chue Hong: 10/28/2005 7:09 AM EST

Comment:

Consistency seems okay.

"Seek Not Permitted Failure	This failure indicates that a seek operation was attempted on a stream that doesn't support seeking.  To avoid this 
failure, clients that wish to use seekRead and seekWrite on a resource that doesn't support seeking should send in seek values indicating an offset of
 0 bytes, and with the seekOrigin set to the current position value.  No specific information is required of the Profile Rendering."

Action:

Update

Neil Chue Hong: 10/28/2005 7:09 AM EST
	Action:	Update artifact_status changed from Open to Closed close_date changed from - to 2005-10-28 13:09:09

Neil Chue Hong: 10/18/2005 11:32 AM EST
	Action:	Create

Return

< Previous

Next >