This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf2620?nav=1 at Sun, 06 Nov 2022 06:58:19 GMT SourceForge : artf2620: (1675) A clarification about concurrency in ByteIO is required (lifetime management)

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Tracker
Project: OGSA-ByteIO-WG     Trackers > ByteIO Specification > View Artifact
Artifact artf2620 : (1675) A clarification about concurrency in ByteIO is required (lifetime management)
Tracker: ByteIO Specification
Title: (1675) A clarification about concurrency in ByteIO is required (lifetime management)
Description:
ISSUE: A clarification about concurrency in ByteIO is required (lifetime
management)
SOLUTION: Add a note saying that this is out of scope and up to implementors. It is a similar example to two processes 
sharing the same stream.
.
Submitted By: Neil Chue Hong
Submitted On: 10/18/2005 11:44 AM EST
Last Modified: 10/28/2005 11:15 AM EST
Closed: 10/28/2005 11:15 AM EST

Status / Comments Change Log Associations Attachments  
Status  
Group: *
Status:* Closed
Category: *
Customer: *
Priority: * 0
Assigned To: * None
Reported in Release: *
Fixed in Release: *
Estimated Hours: * 0
Actual Hours: * 0
Comments
Neil Chue Hong: 10/28/2005 11:15 AM EST
  Comment:
The following has been added in the 28/10/05 version:

"3.	Concurrency in ByteIO

As a simple, file-like bulk data specification, ByteIO explicitly does not address the more complicated question of concurrency for multiple readers 
and writers.  Any attempt at managing such concurrency is left up to external (and undefined) services and software.  Advisory locking could easily be
 implemented as an additional service port type and would not impact the simplicity of ByteIO.  The only concurrency issues that are addressed by 
ByteIO are atomicty issues revolving around multiple read/write requests within the service.  At that level, each ByteIO specific operation (read, 
write, append, etc.) should be atomic.
"
  Action: Update
Neil Chue Hong: 10/28/2005 11:15 AM EST
  Action: Update
artifact_status changed from Open to Closed
close_date changed from - to 2005-10-28 17:15:54
Neil Chue Hong: 10/18/2005 11:44 AM EST
  Action: Create


 
 
 
< Previous
 
 
Next >
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf2620?nav=1 at Sun, 06 Nov 2022 06:58:23 GMT