Author Topic: ProximitySender and many clients  (Read 3143 times)

vlp

  • Guest
ProximitySender and many clients
« on: August 31, 2009, 08:02:19 PM »
I have done a demo application using wclProximitySender object. Although it works fine for a few clients it seems to behave strangely for many of them. I mean that during the search phase it finds almost all the clients (i'm experimenting with around 10 clients) but then it sends the content only to 1, 2 or 3 clients (surely not to all). I might doing something wrong but I would like to know what is the process cycle of the proximitySender? (by the way i have set to be served 5  clients concurrently)

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: ProximitySender and many clients
« Reply #1 on: August 31, 2009, 08:07:21 PM »
Which bluetooth driver do you use? Also what is connect timeout value?

P.S. Please, use specified to Edition topics. WCL looks identical, but internal implementation may be different.

vlp

  • Guest
Re: ProximitySender and many clients
« Reply #2 on: August 31, 2009, 10:33:47 PM »
I use MS bluetooth stack with MSI Star Key 2 dongle. The connect timeout is set to default (I think it's 30).

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: ProximitySender and many clients
« Reply #3 on: September 01, 2009, 06:10:54 AM »
Ok, thanks. Will check.

Online Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: ProximitySender and many clients
« Reply #4 on: September 01, 2009, 12:02:32 PM »
Hi,

it seems to be fixed. Will be available as 6.6.1 soon

 

Sitemap 1 2 3 4 5 6 7 8 9