Receiving side at a MultiPeer Connectivity data stream always returns Stream.Event.hasBytesAvailable Swift4
Well I can start streaming data in peer to peer connection. I get first bunch of data without problem and use it.
The problem is only
case Stream.Event.hasBytesAvailable:
is firing at receiver side so I can not know if received data is consumed or not at sender side.
Besides,
self.outputStream?.streamStatus.rawValue
returns open.
Receiver continues receiving new data which is piling up in receivedData.
After every
let writtenData = data.withUnsafeBytes { self.outputStream?.write($0, maxLength: data.count) }
writtenData have been never 0 or -1 by the way. It is always a value seems to be right amount we are writing.
we are suppose to use data and reset receivedData and wait in sender till receiver side ready.
It feels receiver should inform sender that data is consumed and ready for more in streaming but I could not find how to do it till now.
var receivedData = NSMutableData()
func stream(_ aStream: Stream, handle eventCode: Stream.Event){
switch(eventCode){
case Stream.Event.hasBytesAvailable:
let input = aStream as! InputStream
var buffer = [UInt8](repeating: 0, count: 2048)
let len = input.read(&buffer, maxLength: buffer.count)
receivedData.append(buffer, length: len)
case Stream.Event.endEncountered:
case Stream.Event.hasSpaceAvailable:
case Stream.Event.openCompleted:
case Stream.Event.errorOccurred:
default:
show(text: "default")
}
}
ios streaming swift4
asked Nov 12 at 10:00
Hope
5633828
add a comment |
Well I can start streaming data in peer to peer connection. I get first bunch of data without problem and use it.
The problem is only
case Stream.Event.hasBytesAvailable:
is firing at receiver side so I can not know if received data is consumed or not at sender side.
Besides,
self.outputStream?.streamStatus.rawValue
returns open.
Receiver continues receiving new data which is piling up in receivedData.
After every
let writtenData = data.withUnsafeBytes { self.outputStream?.write($0, maxLength: data.count) }
writtenData have been never 0 or -1 by the way. It is always a value seems to be right amount we are writing.
we are suppose to use data and reset receivedData and wait in sender till receiver side ready.
It feels receiver should inform sender that data is consumed and ready for more in streaming but I could not find how to do it till now.
var receivedData = NSMutableData()
func stream(_ aStream: Stream, handle eventCode: Stream.Event){
switch(eventCode){
case Stream.Event.hasBytesAvailable:
let input = aStream as! InputStream
var buffer = [UInt8](repeating: 0, count: 2048)
let len = input.read(&buffer, maxLength: buffer.count)
receivedData.append(buffer, length: len)
case Stream.Event.endEncountered:
case Stream.Event.hasSpaceAvailable:
case Stream.Event.openCompleted:
case Stream.Event.errorOccurred:
default:
show(text: "default")
}
}
ios streaming swift4
asked Nov 12 at 10:00
Hope
5633828
add a comment |
Well I can start streaming data in peer to peer connection. I get first bunch of data without problem and use it.
The problem is only
case Stream.Event.hasBytesAvailable:
is firing at receiver side so I can not know if received data is consumed or not at sender side.
Besides,
self.outputStream?.streamStatus.rawValue
returns open.
Receiver continues receiving new data which is piling up in receivedData.
After every
let writtenData = data.withUnsafeBytes { self.outputStream?.write($0, maxLength: data.count) }
writtenData have been never 0 or -1 by the way. It is always a value seems to be right amount we are writing.
we are suppose to use data and reset receivedData and wait in sender till receiver side ready.
It feels receiver should inform sender that data is consumed and ready for more in streaming but I could not find how to do it till now.
var receivedData = NSMutableData()
func stream(_ aStream: Stream, handle eventCode: Stream.Event){
switch(eventCode){
case Stream.Event.hasBytesAvailable:
let input = aStream as! InputStream
var buffer = [UInt8](repeating: 0, count: 2048)
let len = input.read(&buffer, maxLength: buffer.count)
receivedData.append(buffer, length: len)
case Stream.Event.endEncountered:
case Stream.Event.hasSpaceAvailable:
case Stream.Event.openCompleted:
case Stream.Event.errorOccurred:
default:
show(text: "default")
}
}
ios streaming swift4
asked Nov 12 at 10:00
Hope
5633828
Well I can start streaming data in peer to peer connection. I get first bunch of data without problem and use it.
The problem is only
case Stream.Event.hasBytesAvailable:
is firing at receiver side so I can not know if received data is consumed or not at sender side.
Besides,
self.outputStream?.streamStatus.rawValue
returns open.
Receiver continues receiving new data which is piling up in receivedData.
After every
let writtenData = data.withUnsafeBytes { self.outputStream?.write($0, maxLength: data.count) }
writtenData have been never 0 or -1 by the way. It is always a value seems to be right amount we are writing.
we are suppose to use data and reset receivedData and wait in sender till receiver side ready.
It feels receiver should inform sender that data is consumed and ready for more in streaming but I could not find how to do it till now.
var receivedData = NSMutableData()
func stream(_ aStream: Stream, handle eventCode: Stream.Event){
switch(eventCode){
case Stream.Event.hasBytesAvailable:
let input = aStream as! InputStream
var buffer = [UInt8](repeating: 0, count: 2048)
let len = input.read(&buffer, maxLength: buffer.count)
receivedData.append(buffer, length: len)
case Stream.Event.endEncountered:
case Stream.Event.hasSpaceAvailable:
case Stream.Event.openCompleted:
case Stream.Event.errorOccurred:
default:
show(text: "default")
}
}
ios streaming swift4
ios streaming swift4
asked Nov 12 at 10:00
Hope
5633828
asked Nov 12 at 10:00
Hope
5633828
edited Nov 13 at 8:01
asked Nov 12 at 10:00
Hope
5633828
asked Nov 12 at 10:00
Hope
5633828
asked Nov 12 at 10:00
Hope
5633828
5633828
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53259761%2freceiving-side-at-a-multipeer-connectivity-data-stream-always-returns-stream-eve%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53259761%2freceiving-side-at-a-multipeer-connectivity-data-stream-always-returns-stream-eve%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
