Marcel Märtens 187ec42aa2 fix Participant shutdown ... - we had the problem that Participants couldn't shutdown them self, only by scheduler, which was controlled by api. it's needed e.g. to handle the Schudown Frame - my initial solution did a full shutdown, which was a problem if in parallel a 2nd shutdown was requested, no possibility of getting the error - new solution will only deactivate Participant and Stream. and then still functions correctly, till the api closes the participant and calls the scheduler which then calls the bparticipant again - i experimented with a Mutex<oneshot> or 2 and a `select` but it didn't prove that well - also adjusted the Error messages to now either Disconnected when gracefully shutdown or ProtocolFailed when some msg couldn't be delivered (note later might not be 100% returned correctly yet)		2020-07-13 13:03:30 +02:00
..
closing.rs	fix Participant shutdown	2020-07-13 13:03:30 +02:00
helper.rs	proper voxygen connect and code cleanups:	2020-07-13 13:03:20 +02:00
integration.rs	proper voxygen connect and code cleanups:	2020-07-13 13:03:20 +02:00