Hi Luiz, On Wed, Oct 01, 2014, Luiz Augusto von Dentz wrote: > -struct bt_gatt_client *bt_gatt_client_new(struct bt_att *att, uint16_t mtu) > +struct bt_gatt_client *bt_gatt_client_new(int fd, uint16_t mtu) This becomes a bit cumbersome since pretty much any time you have a connected ATT socket you must be able to be both client and server in order not to exhibit broken behavior. With the above change you'd need something like the following since the fd should really only be processed in one place (bt_att). client = client_new(fd); att = client_get_att(client); server = server_new(att); Without your change I assume the code has been something like: att = att_new(fd); client = client_new(att); server = server_new(att); The above is fine except I don't really see the point in having separate client and server objects to begin with. I might have missed the reasoning behind it (in which case please enlighten me), but why don't we hide both roles behind the same object, since they're anyway tied to the same connection? I have no objections to having clearly name-spaced functions for client and server side behavior, and even keeping these in separate c-files, but having independent objects for them seems a bit pointless. So why couldn't we have server_foo(att) and client_foo(att) while keeping just this one "att" context? Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
