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
After the v0.8.2 release, many of the good manual links seem to be broken. Is it possible to restore them since the manual pages have very useful content about the usage patterns, API description etc. Thank You.
The manual at that address was pretty out of date and was removed in favor of the (up to date) documentation included in the repository itself (and mirrored at docs.websocketpp.org). The most up to date version of the handler list can be found there: https://docs.websocketpp.org/reference_8handlers.html
I'll make a note to add redirects for pages from the old manual. Other than the handler list, if there are any other entries from the old manual that seem missing from the modern docs let me know and I'll try and track them down.
Thank you very much. The verbosity and the excellent textual description in your old manual was very good for the beginners trying to learn and use websockepp. If you can bring some of that text from the old manual into your new docs inside the repository, that will be immensely helpful for the user community. Documentation and easy-to-understand working examples will go a long way in the wider adoption of the world class, high quality work you are doing with websocketpp.
This is another link from your old manual which talks about an important pattern. Please resurrect that as well in your new docs.
On a different topic: I have tested the fantastic feature addition done by grover and sergeyroots for supporting the persistent HTTP connections. Is there a plan to pull that feature into an upcoming release of websocketpp?
After the v0.8.2 release, many of the good manual links seem to be broken. Is it possible to restore them since the manual pages have very useful content about the usage patterns, API description etc. Thank You.
Http Handler
The text was updated successfully, but these errors were encountered: