NetCURL 6.1 is built as individual modules, so it is possible to communicate directly with each of them . That is actually (initially at least) how we run the unit tests. For all curl based communications, for example, the tests are built with very little interest if the drivers actually exists. So by testing them directly, they are expected to be there. That makes each test package more safe to test without any bridging. This documentation should cover all the waysseparately. If you are sure that curl for example is available regardless of where you put your code, the CurlWrapper can be used instead of NetWrapper. This is also how some of the unit tests are was built initially, to make sure that each module works as intended when it was impemented in NetWrapper (that is the bulked feature of this package). NetWrapper is the module that looks for the most competent driver to handle calls, where curl is the primary choice.
What this section covers
| Child pages (Children Display) |
|---|