mars_nwe/mars-nwe
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases 2 Wiki Activity

docs: record old direct sync layout audit results

Browse Source
This commit is contained in:
bot
2026-06-01 19:37:59 +00:00
committed by Mario Fetka
parent dd64d83979
commit 492befda0d
3 changed files with 28 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
src/nwconn.c
View File

@@ -2755,7 +2755,11 @@ static int handle_ncp_serv(void)
*
* SDK request: no additional request fields.
* SDK reply: no reply data.
* SDK completion: 0x00 success, 0xff failure/lock error.
* SDK completion: 0x00 success.
*
* Compared against the SDK/PDF: the request has no payload after
* FunctionCode. MARS-NWE has no active case for this endpoint, so
* this remains a TODO-only compatibility stub.
*
* TODO: not implemented in MARS-NWE yet.
*
@@ -2772,7 +2776,11 @@ static int handle_ncp_serv(void)
*
* SDK request: no additional request fields.
* SDK reply: no reply data.
* SDK completion: 0x00 success, 0xff failure.
* SDK completion: 0x00 success.
*
* Compared against the SDK/PDF: the request has no payload after
* FunctionCode. MARS-NWE has no active case for this endpoint, so
* this remains a TODO-only compatibility stub.
*
* TODO: not implemented in MARS-NWE yet.
*
@@ -2804,9 +2812,13 @@ static int handle_ncp_serv(void)
* A logged file may name a file that does not exist yet; locking it
* reserves that name for the client. The newer Log File variants
* are 0x2222/105 and 0x2222/87/36, while 0x2222/04 and 0x2222/106
* lock the accumulated file set. MARS-NWE records this old layout
* through nw_log_file(), which is the same table consumed by the
* file-set Lock/Release/Clear handlers below.
* lock the accumulated file set.
*
* Compared against the SDK/PDF: the current INPUT layout matches
* the documented old request offsets and reads LockTimeout in the
* documented Hi-Lo order. MARS-NWE records this old layout through
* nw_log_file(), which is the same table consumed by the file-set
* Lock/Release/Clear handlers below.
*/
struct INPUT {
uint8 header[7]; /* Requestheader */
@@ -3030,6 +3042,10 @@ static int handle_ncp_serv(void)
* They return no reply data and report success or Unlock Error
* through the completion code.
*
* Compared against the SDK/PDF: the current INPUT layout matches
* the documented old request offsets: FunctionCode at offset 6,
* SynchNameLen at offset 7, and SynchName at offset 8.
*
* Important semantic difference: Release Logical Record leaves the
* string in the caller's synchronization string table so a later
* Lock Logical Record Set can relock it. Clear Logical Record