- made override settings for http vs https
- made override settings for well known get vs post
- do not require a long list of settings to be passed in to consturct core
https://github.com/openpeer/op/issues/34
- avoid double auto-applying settings when no settings delegate present before stack is setup
https://github.com/openpeer/op/issues/34
- progres on background fix to better handle TCP connections going to the background
https://github.com/openpeer/opios/issues/200
- removed old method for checking TCP messaging backgrounding checking socket
https://github.com/openpeer/op-services-cpp/issues/10
- Need debug setting to force data over TURN socket
https://github.com/openpeer/op-services-cpp/issues/14

- Need debug setting to force data over TURN TCP socket
https://github.com/openpeer/op-services-cpp/issues/15
- Gracefully close finder connection during backgrounding
https://github.com/openpeer/op-stack-cpp/issues/39

- Gracefully close all peer to peer relay via finder channels during backgrounding
https://github.com/openpeer/op-stack-cpp/issues/42
- Fix: account doesn't need a backgrounding timer anymore
https://github.com/openpeer/op-stack-cpp/issues/43
- fix: account wasn't subscribed to backgrounding
- fix: account would not wait for finder to fully logout before going to background
- fix: finder connection didn't correctly detect that it needed to logout during shutdown
https://github.com/openpeer/op/issues/46
- Have setting to force finder client session refresh to a maximum duration
https://github.com/openpeer/op-stack-cpp/issues/44
- discovered that using $timestamp as a conflict resolver is not the best idea because if finder does not preserve value, each side can think they have won with the latest value when neither side has won. A new "created" value inside proof bundle offers a stable creation timestamp that can be proven to be valid. The trouble is the servers aren't preserving information so it cannot be used at this time so the fallback "context" string is being used to resolve but that means very old dead sessions could be though to win when they must lose.
https://github.com/openpeer/op/issues/48
https://github.com/openpeer/hcs-servers-java/issues/115
- Finder communication should ping with channel '0' "\n" string every 30 seconds
https://github.com/openpeer/op-stack-cpp/issues/45
- Ignore received "\n" from client in case server or peer ever sends ping cycle
https://github.com/openpeer/op-stack-cpp/issues/46
Merge branch 'private-20140227-robin-backgrounding-fix' into 20131025-federated-cloud-contacts

* private-20140227-robin-backgrounding-fix:
  - Ignore received "\n" from client in case server or peer ever sends ping cycle https://github.com/openpeer/op-stack-cpp/issues/46
  - Finder communication should ping with channel '0' "\n" string every 30 seconds https://github.com/openpeer/op-stack-cpp/issues/45
  - discovered that using $timestamp as a conflict resolver is not the best idea because if finder does not preserve value, each side can think they have won with the latest value when neither side has won. A new "created" value inside proof bundle offers a stable creation timestamp that can be proven to be valid. The trouble is the servers aren't preserving information so it cannot be used at this time so the fallback "context" string is being used to resolve but that means very old dead sessions could be though to win when they must lose. https://github.com/openpeer/op/issues/48 https://github.com/openpeer/hcs-servers-java/issues/115
  - Have setting to force finder client session refresh to a maximum duration https://github.com/openpeer/op-stack-cpp/issues/44
  - fix: account wasn't subscribed to backgrounding - fix: account would not wait for finder to fully logout before going to background - fix: finder connection didn't correctly detect that it needed to logout during shutdown https://github.com/openpeer/op/issues/46
  - Fix: account doesn't need a backgrounding timer anymore https://github.com/openpeer/op-stack-cpp/issues/43
  - Gracefully close finder connection during backgrounding https://github.com/openpeer/op-stack-cpp/issues/39
  - Need debug setting to force data over TURN socket https://github.com/openpeer/op-services-cpp/issues/14
  - removed old method for checking TCP messaging backgrounding checking socket https://github.com/openpeer/op-services-cpp/issues/10
  - progres on background fix to better handle TCP connections going to the background https://github.com/openpeer/opios/issues/200
- stack message request monitor needs support to never time-out
https://github.com/openpeer/op/issues/53
- Need a reasonable end of candidates timeout for account peer location (since request never truly times out anymore)
https://github.com/openpeer/op/issues/54
- Account peer location requester side needs to send "peer-location-find" update notifies
https://github.com/openpeer/op-stack-cpp/issues/48

- prepared code for: Account peer location requester side needs to send "peer-location-find" update notifies
https://github.com/openpeer/op-stack-cpp/issues/48
- Account peer location find request should not wait until ICE is fully ready
https://github.com/openpeer/op-stack-cpp/issues/47
- Fix: Account Peer Location was preventing the sending of "peer-location-notifies" until "identify" completed
https://github.com/openpeer/op-stack-cpp/issues/51
- fix: ICE Priority values need to change when IPs are re-arranged in priority order
https://github.com/openpeer/op-services-cpp/issues/26

- fix: ICE Quick route map doesn't take into acount via
https://github.com/openpeer/op-services-cpp/issues/25

- fix: ICE socket unbinding
https://github.com/openpeer/op-services-cpp/issues/23

- false is true and true is false for log and "peer-location-find"
https://github.com/openpeer/op/issues/55