Hi,The implementations on top of OpenOBEX I've done so far all "guess" the optimal size of data chunks to add as body headers (typically something like "MTU - 200"). Would the attached patch for a new OBEX_ObjectGetSpace function make sense that applications could use to get a more precise value for what size body headers they can successfully give to OBEX_ObjectAddHeader (the actual calculation in the patch is directly taken from OBEX_ObjectAddHeader). Or is there already a better/cleaner way to do this with the current openobex API?
Johan
obex-getspace.patch
Description: Binary data
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
