We are not currently documenting and supporting the query parameters and POST data of today's stream manager. There is a good chance it will change in the future. So that is why we don't approach it this way. It is best to build your own HTTPProvider. Then you can control the interface and we do not plan to change this API moving forward.
I hope this helps to clarify the reason for pushing to the HTTPProvider method.
Yes that answered my questions, thank you very much. I'll look into the HTTPProvider method now.