Public comments are a very important part of the OGF document approval process. Through public comments, documents are given scrutiny by people with a wide range of expertise and interests. Ideally, a OGF document will be self-contained, relying only on the other documents and standards it cites to be clear and useful. Public comments of any type are welcomed, from small editorial comments to broader comments about the scope or merit of the proposed document. The simple act of reading a document and providing a public comment that you read it and found it suitable for publication is very useful, and provides valuable feedback to the document authors.
Thank you for making public comments on this document!
Comments for Document: SAGA API Extension: Message API
|Public Comment End:||24 Oct, 2010|
I find the semantic separation of the various requirements (reliability, delivery, etc) quite interesting. I am not familiar with the target use cases, but in general, the detailed specification of requirements could cost latency (considering the potential number of branches). [...] One may need to use different code path's for their implementation - although that should not matter in WAN setups [as the WAN latencies then dominate].
Also interesting is the [inclusion of] multicast. That is somewhat similar to
the MPI Sparse Collectives which I propose for standardization: (http://www.unixer.de/publications/index.php?pub=85).
[FWIW: Torsten also submitted a number of typos etc]