Am Montag 21 Mai 2007 02:38 schrieb Manuel Naranjo: > > Huh? Moving the sdp_* function to d-bus sounds quite strange to me. > > > > For obexpushd, the following question come to my mind: > > What is sdp_connect() and sdp_record_register() is going to look like, > > then? Is there a C API that does not contain a statement like > > "If you use this low-level API directly, you're signing up for some > > pain." ? > > And, at least for me, using the GLib binding is _not_ an acceptable > > solution if this pulls in any GTK or gnome stuff. > > AFAIK you don't have to use Glib to use D-BUS, KDE uses it too. I will > try to take a look at the sources, and let you know how the new sdp > stuff is done. The low level C api is going to be deprecated for a lot > of stuff, furthermore some parts will not be accessible, AFAIK it's > supposed to be much easier than the C api, but I don't know
Hmm, looking at wiki.bluez.org, I think that it will be easy for the bluez guys to provide a library that does the d-bus stuff and is compatible to the current one. I don't think that every app out there should use those I_could_not_find_a_short_name_for_this() d-bus functions with magic strings being the API. We'll see where this leads to. Just do me a favour: do not provide any API that only allows obex over bluetooth (thus repeating the mistakes from Microsoft and Apple) as application probably will be using that and, as the consequence, do not support other transports. HS ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
