267254 - need PRIOVec that matches OS capabilities

Status: RESOLVED WONTFIX

(NSPR :: NSPR, enhancement)

Description

[Julien Pierre]

In some 64-bit operating systems, iov_len in iovec is a 64-bit quantity.
The PRIOVec/ PR_WriteV combination does not allow using 64-bit quantities in IO
vectors because iov_len is defined as "int" within PRIOVec.

We can't change PRIOVec and PR_WriteV for binary compatibility reasons.

I propose that we implement a new function which takes an iovec that matches th
OS underneath. I would propose to define PRIOVecNative and PR_WriteVNative .

This is needed for one of our applications which uses its own NSPR I/O layer,
but has a writev API of its own that takes a native iovec, which has length that
may be larger than the PRIOVec.

Without this NSPR enhancement, the application would have to screen the PRIOVec
in its layer for >int iov_len sizes, and either fail or split the data into
multiple writes.

Comment 1

[Julien Pierre]

This is actually not a good idea. We should provide a platform-independent
interface. We should just migrate to 64-bit size in IOVec when it is needed.
Resolving this WONTFIX.