-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow answer #83
Comments
Checkout your Internet uplink, remove unused code that may increase your task working time. |
easier said than done :) unused code shouldnt increase the task working time no? but basically you are telling me that i need to remove some validation code the process dont really need to work? Sorry im more a database programmer than a web programmer and i never did the part where i got to connect so i'm mostly trying to figure it out. |
It probably your long polling, sometimes LINE kinda buggy (like there's already new Op, but long polling not emitted new one, or it just like... died socket). Oh ya one thing, LINE didn't actually handshake https like you'll understand this uri scheme [:proto]://[:host][:ssl_proto_default_port]/[:uri] (gist code) |
@anysz i thought that the long polling was the action(events) received?..... because that part is really quick. if i can ask you something else.... do you have any idea how the bot could download an image sent by an other user? |
Hi,
is there anyone who know how to reduce the answer time to respond?
i read on some place that someone figured how to use the protocol S3( like the official bot is using) instead of S4 (like we are using in line-py) and it reduce from 6 second to 0.4 sec (way faster like the official bot).
Any idea?
This is the other place im talking about but its using the same base as line-py
(yes i read that we had to modify thrift and config)
ruyaoyao/LINE-instant-messenger-protocol#5
Thanks
The text was updated successfully, but these errors were encountered: