Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
Guillaume's branch is already a good start. I think we should already merge that part since it's pretty-much straightforward (copied from TpStreamTubeChannel). It is just missing factory integration to be ready to merge IMO.
So needs a _tp_dbus_tube_channel_new_with_factroy() and use it in TpAutomaticClientFactory.
This would be really nice to have available to LibreOffice last week, so I'm looking at quickly polishing enough of this up to let them delete some handrolled code. :)
It looks like this stalled partly due to bug 41323.
Here is a branch based on Guillaume's branch with one commit amended, and re-Authored to me, and some other commits.
I've reviewed all of Guillaume's code and it either looks fine or I've fixed it.
I've omitted the top WIP patch from Guillaume's branch which deals with name owner tracking, which I presume is blocked on bug 41323. It's not needed for 1-1 tubes anyway.
And I dodged the question of how to support specifying LOCALHOST as the access control because, frankly, the only platform that needs it is Sugar.
/* FIXME: this is pretty stupid but apparently unless you start and then
* stop the server before freeing it, it doesn't stop listening. Calling
* _start() twice is a no-op.
*/
Sounds like a GDBusServer bug no? Did you report it?
/* FIXME: this isn't a particularly good error… it's just what comes out when
the channel gets closed from under us, and there isn't really API on
DBusTube to give a better error.
*/
I think we should have some way to say if the receiver rejected the tube invitation. Open a spec bug?
"DBusTubeChannel: always use CREDENTIALS for now"
I agree. Specific system like Sugar can easily patch this and we can always use a tp_dbus_tube_channel_use_localhost_crendetial () later if we really need to.
Ideally I'd prefer have more examplary examples using GDBus's code generation but that will do for now.
I've omitted the top WIP patch from Guillaume's branch which deals with name
owner tracking, which I presume is blocked on bug 41323. It's not needed for
1-1 tubes anyway.
Yeah it's block on it. Could you please open a new bug once this one if merged/closed?
I ported the feature/tubes2 branch of LibreOffice to use this branch to check that it works (attached). I was a little disappointed that it didn't save more code. The main reason, I think, is that the paths which call _offer_async() and _accept_async() are essentially identical but have to be duplicated.