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
Now tcpsock:receive now support two pattern '_a' and '_l'(default '*l' if pattern is nil), it's quite useful in text-based protocol or open binary protocol(eg. Mysql).
But to deal with non-public protocol, we need stream reading pattern, return anything once socket receives.
For example, we hava a decode library(.so/.dll) privided by others who don't open their protocol, and we need to fill socket data into the library to decode message out. Without steam reading pattern, decode can't be done in efficient way (done by tcpsock:receive(1) loop).
I suggest to add stream reading pattern into tcpsock:receive, especially in stream-lua-nginx-module
The text was updated successfully, but these errors were encountered:
mike07026
changed the title
tcpsock:receive need stream reading pattern
tcpsock:receive needs stream reading pattern
Aug 30, 2016
Uh oh!
There was an error while loading. Please reload this page.
Now tcpsock:receive now support two pattern '_a' and '_l'(default '*l' if pattern is nil), it's quite useful in text-based protocol or open binary protocol(eg. Mysql).
But to deal with non-public protocol, we need stream reading pattern, return anything once socket receives.
For example, we hava a decode library(.so/.dll) privided by others who don't open their protocol, and we need to fill socket data into the library to decode message out. Without steam reading pattern, decode can't be done in efficient way (done by tcpsock:receive(1) loop).
I suggest to add stream reading pattern into tcpsock:receive, especially in stream-lua-nginx-module
The text was updated successfully, but these errors were encountered: