WIP: Support outgoing tracking of requests with Java

[matthewoates]

Some outstanding questions:

• It still makes sense to track transactionId right? I can add a getTransactionId hook
• Do I need to call ipAddress and leverage similar logic to https://github.com/Moesif/moesif-servlet/blob/master/moesif-servlet/src/main/java/com/moesif/servlet/utils/IpAddress.java ?
• I don't think the response body parsing is very versatile. What would you recommend here when working with something as generic as an InputStream?
• Is transferEncoding still needed?
• Should we add an apiToken hook? It doesn't look like it's used in servlet.
• What's best practice for logging warnings / errors? System.out.println with a debug option in config that defaults to false?

TODO:

• hook up apiVersion hook
• migrate local testing code into separate example repo

[dgilling]

Ignore TransactionId.
Yes, we should still grab the address like we do in Express and Python since it's dependent on the header, env.
transferEncoding is needed when body is not JSON. We use it to base64 encode the binary data. This means transferEncoding is set to 'base64'
See: https://www.moesif.com/docs/api#events and https://github.com/Moesif/moesif-express/blob/master/lib/index.js

[dgilling]

You can use that or import something like log4j or java.util.logging

[matthewoates]

@dgilling is this how we should handle requests that fail? I think they should be reported to moesif somehow. 500 probably isn't the right status code either.