Skip to content
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

Add information for using WResource #191

Conversation

limitedAtonement
Copy link
Contributor

I didn't see any other documentation that lays this pointer out, so I think this is the best place for it.

It might also be helpful to point to a pertinent example such as blog.C:49 or the URL Params example (lines 53 and following).

It took me a while to figure out how to install a custom Wt::WResource
in my Wt::WApplication. A little tip off here would have helped a good
deal.
@limitedAtonement
Copy link
Contributor Author

Please let me know if something should be changed here to make it suitable for inclusion in the project, or if you reject the pull request, I'll be happy to close.

@@ -86,6 +86,10 @@ enum class ContentDisposition {
* \endcode
* \endif
*
* In order to configure your web server to serve such a resource, either
* create a link to it using WAnchor or WImage, or add it to your WServer
* using WServer::handleRequest().
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume you mean addResource, not handleRequest.

Also: The "global and private resources" heading already makes mention of it. The only thing that's lacking is how to serve a private resource (i.e. through a WLink).

@limitedAtonement
Copy link
Contributor Author

I think you're right: this is adequately addressed already. Thank you!

@limitedAtonement limitedAtonement deleted the wresource-documentation branch October 25, 2022 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants