You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2020. It is now read-only.
RtmpClient have asynchronous methods.
But it is not like asynchronous method for Windows Runtime.
Developers will suffer the disadvantage of some in status quo.
Developers of C# or VB can't await asynchronous methods of RtmpClient.
Developers of all programming languages can't know of the exception in the asynchronous processing.
So, We change should be asynchronous method for RtmpClient to Windows Runtime style.
Return IAsyncAction/IAsyncOperation.
Change method name Windows Runtime style.
ex:
Connect method name to ConnectAsync method name.
If you agree with this proposal, I will do this.
The text was updated successfully, but these errors were encountered:
Developers of C# or VB can't await asynchronous methods of RtmpClient.
Methods don’t have to wait process.
Developers cannot care connection thread. It’s easy to program.
(If async methods is opened, developers care threads around. Its development is not agile.)
Developers of all programming languages can't know of the exception in the asynchronous processing.
Developers cannot care exception.
When happened exception, connection thread abort. It indicate connection is closing.
Methods don’t have to wait process.
Developers cannot care connection thread. It’s easy to program.
(If async methods is opened, developers care threads around. Its development is not agile.)
Developers should can decide to wait method, do not wait method.
We decide is not.
How they can know method completed?
Certainly, Connect method can notify by events.
But, it is not intuitive.
And, developers not much care about IAsyncAction/IAsyncOperation .
Developers cannot care exception.
When happened exception, connection thread abort. It indicate connection is closing.
No.
Developers should care exception.
Or else, They can not notify failure information to user.
They should can decide notify or not notify.
Also, Internal StreamSocket throw exception when Connect.
I guess application will abort at that time.
However, I do not yet fully understand the current code.
please answer in stride.
And, if I am wrong I'm sorry.
Thanks.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
RtmpClient have asynchronous methods.
But it is not like asynchronous method for Windows Runtime.
Developers will suffer the disadvantage of some in status quo.
So, We change should be asynchronous method for RtmpClient to Windows Runtime style.
ex:
Connect method name to ConnectAsync method name.
If you agree with this proposal, I will do this.
The text was updated successfully, but these errors were encountered: