Refactor peer protocol handling

[sevenbitbyte]

Should refactor RTCPeerComms.handleClientCall into some sort of host protocol handler.

• Authenticate actor
• Mode select
  • rest
    • peer-party
    • custom peer endpoints []
  • peer-socket
    • Document change - /dataparty/document/${type}/${id}

dataparty-api/src/comms/rtc-socket-comms.js

Lines 29 to 67 in 540ae17

	async handleClientCall(message){
	let response = null
	const request = await this.decrypt( {data: message}, this.remoteIdentity )
	debug('handleHostCall', request)
	if(!this.authed){
	if(request.op == 'auth'){
	debug('allowing client')
	response = {
	op: 'status',
	id: request.id,
	level: 'Info',
	state: 'Finished_Success'
	}
	clearTimeout(this._host_auth_timeout)
	this._host_auth_timeout = null
	this.authed = true
	this.emit('open')
	this.send(response)
	}
	return
	}
	if (request.op == 'peer-call') {
	debug('peer-call')
	if(request.endpoint == 'api-v2-peer-bouncer'){
	debug('ask->',request.data)
	this.send({
	op: 'status',
	id: request.id,
	state: 'Finished_Success',
	...await this.party.handleCall(request.data)
	})
	}
	}
	}

[sevenbitbyte]

See #39 "improve the peer comms protocol and expected behavior of hosts."

[sevenbitbyte]

One approach to enable endpoints could be to use express mock libraries

https://www.npmjs.com/package/node-mocks-http

https://www.npmjs.com/package/mock-express-response

https://www.npmjs.com/package/mock-req-res