actually i am facing a problem in creating multiple sessions with create session here is the scenario i am doing …

i scan for devices allocate files to each one then start a thread for each device the thread CreateSession then send files to the device then Disconnect and Close the session

but i am facing a very low performance and the Errors happening with CreateSession and the connection with dbus

and i do not why that happen while when i am sending to only one device every time it sends ok without any problems

if u can support me with some information i will be grateful

cheers,
HusseinCoder

Check out http://svn.muiline.com/cgi-bin/viewvc.cgi/obex-data-server/tags/REL-0_3_3/test/ for sample code. There are two python scripts for creating session and server, they should be helpful.

Cheers,
Tadas

I feel in a continual state of “guess!”. I don’t even know what/if need to call anything to set it up. And so of the stuff on the documentation page ( at http://svn.muiline.com/cgi-bin/viewvc.cgi/obex-data-server/tags/REL-0_3_3/dbus-api.txt ) could be slightly more helpful.

For instance, the first method:

object CreateBluetoothSession(string address, string pattern)

appears to return an object. I wonder what type that object might be, and if it has a related *.h file anywhere? Or maybe it is an object, and I
shouldn’t call it????

You must have some code lying around somewhere to test obex-data-server. Posting at least that (and
perhaps sending it to me, or maybe a link) would
something of a help.

thanks,

=Arthur

ps: Or maybe appearently cryptic documentation would all be crystal clear if I spent a month or two reading through D-Bus and BlueZ code…
my apologies if that is my error.

Cheers,
Tadas

i am developing a project with the obex data server

and i am stuck now in one of the requirements, its

sending multiple files to the user, and the user has

to accept only once for the files but actuall i am

not sure that this is applicable in the obex data

or can be done.

if its can be done and i wish so please support me with some information.

note: the programming language i am using is C.

thank you,

HusseinCoder

Guys I have to get out my hat and congratulate you all.

Lots of bugs had been fixed, specially memory allocation stuff, I left a server running yesterday on the office, and after almost 24 hours, and after 400 sessions created it still works without any trouble.

I also checked with valgrind, and compared 0.3.1 and 0.3.2 and the difference is enormous, from lots of memory corruptions you have moved to 0. Incredible.

Great job everyone,

Thanks,
Manuel

Congratulations on this release! I know you’ve worked very hard to get it ready, we really appreciate the hard work, well done. *thumbs up

Heston

Cheers,
Tadas

So long with no talk, how are things?.

As I told you before we were going to Chicago for a sensors expo. We had a fun time, during the 3 days the sensor lasted ODS received over 2k obex messages from 10 of our devices.

ODS was a bit unstable it crashed no less than 10 times during the expo. I’m going to try this new version and tell you my results.

I tried debuggin and working on fixes to it, but it was impossible.

BTW to all those who all ready don’t know. I’ve found a work around to avoid loosing obex transfers. The solution is registering for dbus signals before the session object is created. I know this is not a nice looking solution, but it has 2 positives results. One is that you don’t loose any message, the other one is that in cases when you’re expecting to receive lots of transfers you are not registering/deregistering from dbus avoiding all the payload related to it.

If you want to take a look at the source it’s available at: http://code.google.com/p/aircable/source/browse/tools/messages

Thanks and good luck to all of you,
Manuel Naranjo
http://www.aircable.net

Well done on this release, those are a handy couple of bug fixes I grabbed this latest version and placed it on my system this morning and it appears to be running just right.

I know we’ve been looking at some fairly substantial changes to the API for the 0.4 release which requires a fair amount of work, we really appreciate the time you and the other decelopers have been putting into this project.

Am I right in assuming that 0.4 is currently earmarked for May/June time release? is there anything I can offer to help the process along?

I was also thinking that a developers IRC channel might of good use, I know there are only a few of us contributing on the bugs list but it would be nice for us to be able to conference chat in real time. What do you think?

Cheers again Tadas, *thumbs up

Robert