“The optional oneway keyword indicates that best-effort semantics are expected of requests for this operation; the default semantics are exactly-once if the operation successfully returns results or at-most-once if an exception is returned.”

Later it says:

“When a client invokes an operation with the oneway attribute, the invocation semantics are best-effort, which does not guarantee delivery of the call; best-effort implies that the operation will be invoked at most once.”

Best-effort execution is described as follows:

“Best-effort: a best-effort operation is a request-only operation (i.e., it cannot return any results and the requester never synchronizes with the completion, if any, of the request).”

I don’t know what you mean by “maybe semantics”, if this is something from the spec, please leave a reference. The combination of “exactly-once in the working case” and “at-most-once in error case” seems to be usually combined to “at-most-once” as behavioural description of oneway functions. Feel free to comment again.

I also don’t know where you found a statement about blocking clients.

oneway has maybe semantics, not at least once.
also, the client does not block on oneway requests.

1. modify the file,
2. don’t save but typeset, then
3. ls -a in the folder where I keep the paper.

Thanks,

Nathan