Hi Mike, unfortunately it's not always possible to get the session state from X2Go server. One simple example - direct RDP session. Another use case, sometimes (for example because of security reasons), you can't have access from X2Go Broker to X2Go Server. Anyway if you are running the network with many clients, different kinds of sessions (X2GO, XDMCP, RDP, DRDP), you'll appreciate the information that you can collect from X2Go Clients.
regards Alex Am 14.12.18 um 10:05 schrieb Mike Gabriel: > Hi Alex, > > On Mi 22 Aug 2018 09:01:15 CEST, Oleksandr Shneyder wrote: > >> Hi Mike, >> >> this feature is activated by broker. If broker is not supporting it, >> there are no changes in X2Go Client behavior. I never putting in master >> branch commits that supposed to break compatibility with previous >> versions. >> >> best regards >> Alex > > I have been looking into the events handling stuff once more and wonder > what use case scenario you had in mind when adding the ability to > TERMINATE or SUSPEND sessions from the broker via the client side? > > The broker can suspend/terminate sessions server-side and the X2Go > Client will follow automatically. > > I understand that retrieving status information from the client is a > nice thing to have, but what problem did you solve with the effort of > adding the events code to X2Go Client? > > Thanks+Greets, > Mike > -- ----------------------------------------------------------- Oleksandr Shneyder | Email: [email protected] phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 -----------------------------------------------------------
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
