[DiscordArchive] And how would multithreaded read or write work?
[DiscordArchive] And how would multithreaded read or write work?
Original source
And how would multithreaded read or write work?
rektbyfaith
06-18-2018, 02:29 PM #1Archived author: Deleted User • Posted: 2018-06-18T14:29:18.881000+00:00
Original source
And how would multithreaded read or write work?
Original source
So you give it the end offset in the first call, then the start offset in the second call
rektbyfaith
06-18-2018, 02:29 PM #2Archived author: Quantam • Posted: 2018-06-18T14:29:32.597000+00:00
Original source
So you give it the end offset in the first call, then the start offset in the second call
Original source
In fact it is good that the kernel handles that for you rather than applications having to handle shared ownership between threads.
rektbyfaith
06-18-2018, 02:29 PM #3Archived author: schlumpf • Posted: 2018-06-18T14:29:34.109000+00:00
Original source
In fact it is good that the kernel handles that for you rather than applications having to handle shared ownership between threads.
Original source
So you mean they should have only a readAt method
rektbyfaith
06-18-2018, 02:30 PM #4Archived author: Deleted User • Posted: 2018-06-18T14:30:01.737000+00:00
Original source
So you mean they should have only a readAt method
Original source
Quantam has a point that `read (pos, size) -> byte[]` is a better API than `seek& (pos); read& (size) -> byte[]`.
rektbyfaith
06-18-2018, 02:30 PM #5Archived author: schlumpf • Posted: 2018-06-18T14:30:14.025000+00:00
Original source
Quantam has a point that `read (pos, size) -> byte[]` is a better API than `seek& (pos); read& (size) -> byte[]`.
Original source
That’s alright
rektbyfaith
06-18-2018, 02:30 PM #6Archived author: Deleted User • Posted: 2018-06-18T14:30:45.566000+00:00
Original source
That’s alright
Original source
I thought you envisioned the Java’s no seek stream api
rektbyfaith
06-18-2018, 02:31 PM #7Archived author: Deleted User • Posted: 2018-06-18T14:31:06.840000+00:00
Original source
I thought you envisioned the Java’s no seek stream api
Original source
You cannot reposition streams
rektbyfaith
06-18-2018, 02:31 PM #8Archived author: Deleted User • Posted: 2018-06-18T14:31:17.792000+00:00
Original source
You cannot reposition streams
Original source
Having separate handles for every thread is a bunch of extra kernel objects that are entirely unnecessary
rektbyfaith
06-18-2018, 02:31 PM #9Archived author: Quantam • Posted: 2018-06-18T14:31:41.926000+00:00
Original source
Having separate handles for every thread is a bunch of extra kernel objects that are entirely unnecessary
Original source
And falls over and dies if you're doing async I/O with a ton of queued requests
rektbyfaith
06-18-2018, 02:32 PM #10Archived author: Quantam • Posted: 2018-06-18T14:32:08.038000+00:00
Original source
And falls over and dies if you're doing async I/O with a ton of queued requests
1 Guest(s)
1 Guest(s)