Azure/DotNetty issues and pull requests

#565 - Can we run it on NET 5.0

Issue - State: open - Opened by Tochemey about 3 years ago

#564 - DotNetty v0.7.0 enforces .NET 5

Issue - State: closed - Opened by tomkerkhove about 3 years ago - 7 comments

#564 - DotNetty v0.7.0 enforces .NET 5

Issue - State: closed - Opened by tomkerkhove about 3 years ago - 7 comments

#564 - DotNetty v0.7.0 enforces .NET 5

Issue - State: closed - Opened by tomkerkhove about 3 years ago - 7 comments

#564 - DotNetty v0.7.0 enforces .NET 5

Issue - State: closed - Opened by tomkerkhove about 3 years ago - 7 comments

#564 - DotNetty v0.7.0 enforces .NET 5

Issue - State: closed - Opened by tomkerkhove about 3 years ago - 7 comments

#564 - DotNetty v0.7.0 enforces .NET 5

Issue - State: closed - Opened by tomkerkhove about 3 years ago - 7 comments

#563 - plan to rewrite this repository with netcore ?

Issue - State: closed - Opened by xyfy about 3 years ago - 1 comment

#563 - plan to rewrite this repository with netcore ?

Issue - State: closed - Opened by xyfy about 3 years ago - 1 comment

#562 - No xthread

Pull Request - State: closed - Opened by nayato about 3 years ago

#562 - No xthread

Pull Request - State: closed - Opened by nayato about 3 years ago

#562 - No xthread

Pull Request - State: closed - Opened by nayato about 3 years ago

#562 - No xthread

Pull Request - State: closed - Opened by nayato about 3 years ago

#562 - No xthread

Pull Request - State: closed - Opened by nayato about 3 years ago

#561 - target net472 and netstandard2.0

Pull Request - State: closed - Opened by ailn over 3 years ago

#561 - target net472 and netstandard2.0

Pull Request - State: closed - Opened by ailn over 3 years ago

#561 - target net472 and netstandard2.0

Pull Request - State: closed - Opened by ailn over 3 years ago

#561 - target net472 and netstandard2.0

Pull Request - State: closed - Opened by ailn over 3 years ago

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#560 - fixed Base64Encoder big bug

Pull Request - State: open - Opened by jacksonjim over 3 years ago - 1 comment

#559 - Why Base64Encoder use the Decode function ?? extend with MessageToMessageDecoder

Issue - State: open - Opened by jacksonjim over 3 years ago

#559 - Why Base64Encoder use the Decode function ?? extend with MessageToMessageDecoder

Issue - State: open - Opened by jacksonjim over 3 years ago

#558 - PriorityQueue

Issue - State: open - Opened by iamkisly over 3 years ago - 1 comment

#558 - PriorityQueue

Issue - State: open - Opened by iamkisly over 3 years ago - 1 comment

#558 - PriorityQueue

Issue - State: open - Opened by iamkisly over 3 years ago - 1 comment

#558 - PriorityQueue

Issue - State: open - Opened by iamkisly over 3 years ago - 1 comment

#558 - PriorityQueue

Issue - State: open - Opened by iamkisly over 3 years ago - 1 comment

#557 - Update to NetStandard 2.0

Pull Request - State: closed - Opened by joebeernink over 3 years ago

#557 - Update to NetStandard 2.0

Pull Request - State: closed - Opened by joebeernink over 3 years ago

#557 - Update to NetStandard 2.0

Pull Request - State: closed - Opened by joebeernink over 3 years ago

#557 - Update to NetStandard 2.0

Pull Request - State: closed - Opened by joebeernink over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#556 - Not sure why getting this could not locate assembly

Issue - State: open - Opened by Abhi2109 over 3 years ago

#555 - has move to SpanNetty

Issue - State: open - Opened by yhj200722 over 3 years ago

#555 - has move to SpanNetty

Issue - State: open - Opened by yhj200722 over 3 years ago

#555 - has move to SpanNetty

Issue - State: open - Opened by yhj200722 over 3 years ago

#555 - has move to SpanNetty

Issue - State: open - Opened by yhj200722 over 3 years ago

#555 - has move to SpanNetty

Issue - State: open - Opened by yhj200722 over 3 years ago

#555 - has move to SpanNetty

Issue - State: open - Opened by yhj200722 over 3 years ago

#554 - The repository is dead?

Issue - State: open - Opened by codeex over 3 years ago - 3 comments

#554 - The repository is dead?

Issue - State: open - Opened by codeex over 3 years ago - 3 comments

#554 - The repository is dead?

Issue - State: open - Opened by codeex over 3 years ago - 3 comments

#554 - The repository is dead?

Issue - State: open - Opened by codeex over 3 years ago - 3 comments

#554 - The repository is dead?

Issue - State: open - Opened by codeex over 3 years ago - 3 comments

#554 - The repository is dead?

Issue - State: open - Opened by codeex over 3 years ago - 3 comments

#553 - MQTT PUBLISH packet encoder splits the topic and payload into different frames

Issue - State: open - Opened by abhipsaMisra over 3 years ago - 2 comments

#553 - MQTT PUBLISH packet encoder splits the topic and payload into different frames

Issue - State: open - Opened by abhipsaMisra over 3 years ago - 2 comments

#553 - MQTT PUBLISH packet encoder splits the topic and payload into different frames

Issue - State: open - Opened by abhipsaMisra over 3 years ago - 2 comments

#553 - MQTT PUBLISH packet encoder splits the topic and payload into different frames

Issue - State: open - Opened by abhipsaMisra over 3 years ago - 2 comments

#553 - MQTT PUBLISH packet encoder splits the topic and payload into different frames

Issue - State: open - Opened by abhipsaMisra over 3 years ago - 2 comments

#553 - MQTT PUBLISH packet encoder splits the topic and payload into different frames

Issue - State: open - Opened by abhipsaMisra over 3 years ago - 2 comments

#552 - ".Option(ChannelOption.ConnectTimeout, timespan)" doesn't shorten the "clientBootstrap.ConnectAsync()" try-connect time.

Issue - State: closed - Opened by solidcomer over 3 years ago - 1 comment

#552 - ".Option(ChannelOption.ConnectTimeout, timespan)" doesn't shorten the "clientBootstrap.ConnectAsync()" try-connect time.

Issue - State: closed - Opened by solidcomer over 3 years ago - 1 comment

#552 - ".Option(ChannelOption.ConnectTimeout, timespan)" doesn't shorten the "clientBootstrap.ConnectAsync()" try-connect time.

Issue - State: closed - Opened by solidcomer over 3 years ago - 1 comment

#552 - ".Option(ChannelOption.ConnectTimeout, timespan)" doesn't shorten the "clientBootstrap.ConnectAsync()" try-connect time.

Issue - State: closed - Opened by solidcomer over 3 years ago - 1 comment

#552 - ".Option(ChannelOption.ConnectTimeout, timespan)" doesn't shorten the "clientBootstrap.ConnectAsync()" try-connect time.

Issue - State: closed - Opened by solidcomer over 3 years ago - 1 comment

#552 - ".Option(ChannelOption.ConnectTimeout, timespan)" doesn't shorten the "clientBootstrap.ConnectAsync()" try-connect time.

Issue - State: closed - Opened by solidcomer over 3 years ago - 1 comment

#551 - Why is ChannelRead not executed?

Issue - State: open - Opened by xiazhaozhao over 3 years ago

#551 - Why is ChannelRead not executed?

Issue - State: open - Opened by xiazhaozhao over 3 years ago

#551 - Why is ChannelRead not executed?

Issue - State: open - Opened by xiazhaozhao over 3 years ago

#551 - Why is ChannelRead not executed?

Issue - State: open - Opened by xiazhaozhao over 3 years ago

#550 - How can I get remote client mac address

Issue - State: open - Opened by willhuo over 3 years ago

#550 - How can I get remote client mac address

Issue - State: open - Opened by willhuo over 3 years ago

#550 - How can I get remote client mac address

Issue - State: open - Opened by willhuo over 3 years ago

#550 - How can I get remote client mac address

Issue - State: open - Opened by willhuo over 3 years ago

#550 - How can I get remote client mac address

Issue - State: open - Opened by willhuo over 3 years ago

#550 - How can I get remote client mac address

Issue - State: open - Opened by willhuo over 3 years ago

#549 - Maybe a bug in DotNetty.Codecs.Http

Issue - State: open - Opened by qianqians over 3 years ago

#549 - Maybe a bug in DotNetty.Codecs.Http

Issue - State: open - Opened by qianqians over 3 years ago

#549 - Maybe a bug in DotNetty.Codecs.Http

Issue - State: open - Opened by qianqians over 3 years ago

#549 - Maybe a bug in DotNetty.Codecs.Http

Issue - State: open - Opened by qianqians over 3 years ago

#549 - Maybe a bug in DotNetty.Codecs.Http

Issue - State: open - Opened by qianqians over 3 years ago

#548 - No traffic handlers ported

Issue - State: open - Opened by tlf30 over 3 years ago

#548 - No traffic handlers ported

Issue - State: open - Opened by tlf30 over 3 years ago

#548 - No traffic handlers ported

Issue - State: open - Opened by tlf30 over 3 years ago

#548 - No traffic handlers ported

Issue - State: open - Opened by tlf30 over 3 years ago