>> Yes. My proposed PBAP storage API follows this rule, but lacks the >> method to unregister the operations. Will add it later. > > I put some prototype declarations into the obexd repository. The > important part is that we have to do this in an async way. We can't > block while retrieving the phonebook information. > I'm implementing PBAP driver framework and a simple(or prototype) PBAP driver based on your prototype declarations. Will add some extentions to the prototype declarations if necessary. To do that in an async way I think the basic idea is: 1 when PBAP driver is loaded(or initialized), fork() is invoked to run PBAP driver in child process 2 the Unix domain socket is used to communicate between PBAP server and PBAP driver; and PBAP server acts as client role at the one end of socket, PBAP driver acts as server role at the other end of socket 3 everytime a PBAP client connects to PBAP server(i.e. a OBEX session is initiated), PBAP server initiates a session(or a socket) with PBAP driver by invoking connect(). Then PBAP server sends subsequent PBAP request(pullphonebook, pullvcardlisting, pullvcardentry) through this socket; PBAP driver sends back the requested data through the socket asyncronously. Am I right? I'd like to first make the basic design ideas clear in order to avoid the unnecessary misunderstanding or confusion before starting to write the code. Thanks, Forrest -- 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
