Jira Issue: WP-10
PZP-PZP Find Services
Changes Done:

RPC: Remote service search for connected peers
PZH_SessionHandling: PZPUPdate message sent after receiving PZP Details message from PZP
PZP_SessionHandling: Different state handling
Session_Schema: Schema not working commented out
PZP_Server: Handling find services in the data event
PZP_WebSocket: ConnectedApp of PZP called for updating address of websocket connection. Schema is not working commented out in the latest branch
Jira Issue# WP-10

Only hubless mode is working now.

Changes done:
- state of different pzp states handled correctly
- connected peer check in rpc now checks array length properly
Jira Issue# WP-6

Updated RPC to handle connected peer length correctly and also register service happens before PZP server is started
Jira Issue: WP-10 PZP-PZP Service discovery

Merge remote-tracking branch 'upstream/master' into WP-10-PZP-PZP-ServiceDiscovery

Conflicts:
	webinos/pzh/lib/pzh_sessionHandling.js
	webinos/pzp/lib/pzp_server.js
	webinos/pzp/lib/pzp_sessionHandling.js
	webinos/pzp/lib/pzp_websocket.js
Jira Issue: WP-10 PZP-PZP Service Discovery

Updated changes from Alex
Added various different states and mode for pzp mode
PZP client and server functionality separated
Changed indentation in few files
Changed context-code changed to auth-code
Added preference to select peer mode or hub mode

Regenerate your certificates to get this working
Use length framing instead of delimiter for JSON over socket

For each JSON string serialized message object to send, use a Buffer
prefixed with four octets for an unsigned int (little endian) that
specifies the length of the serialized message.

Fixes Jira-issue: WP-49
Fix debug message call.

Jira-issue: WP-49
Fix log calls with typod error type. Again.

The wrong type for these log output calls resulted in errors not being
logged.

Jira-issue: WP-49
Merge pull request #21 from aldafu/WP-49-remove-json-msg-delimiter

Use length framing instead of delimiter for JSON over socket
Merge pull request #23 from mlasak/master

Jira issue: WP-57 changing configuration parameters on pzp start up has no effect
Fix how to check if connected to PZH.

So we don't ask the PZH for available services when the PZH has
disappeared.

Jira-issue: WP-10
Merge pull request #2 from aldafu/WP-10-PZP-PZP-ServiceDiscovery-after-rebase

Wp 10 pzp pzp service discovery after rebase
Jira Issue: WP-10 PZP-PZP Service Discovery

This fix will require deleting old files in ~/.webinos/config.

- Corrected indentation in files
- auth-code introduced instead of context-code
- preference to select connect via pzh or direct peer connection
- virgin pzp mode corrected
- few hub and state changes handling
Jira Issue: WP-10 PZP-PZP Service Discovery

Merge to latest on master branch
Virgin PZP mode can now be loaded in case of error connecting to PZH Server
State and Mode checking in RPC
Jira Issue: WP-10 PZP-PZP Service Discovery

Merge remote-tracking branch 'upstream/master' into WP-10-PZP-PZP-ServiceDiscovery

Conflicts:
	webinos/pzh/lib/pzh_sessionHandling.js
	webinos/pzp/lib/pzp_sessionHandling.js
	webinos/pzp/lib/session_common.js
Merge pull request #24 from habibvirji/WP-10-PZP-PZP-ServiceDiscovery

Jira Issue: WP 10 PZP-PZP Service discovery
Added maven profiles (windows, linux, android)

Jira Issue: WP-62
Updated comments in pom files

Jira issue: WP-62
Merge pull request #25 from pshapovalov/maven-profiles

Maven profiles (Jira issue: WP-62)
Remove dependencies from node_modules/.

NPM will install our dependencies.

Jira-issue: WP-64