Author Topic: Voice Platform:number of outstanding requests  (Read 4748 times)

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1416
  • Karma: 18
Voice Platform:number of outstanding requests
« on: August 22, 2007, 06:07:07 PM »
Is there a maximum number of outstanding messages per one Platform SDK protocol object?


Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: Voice Platform:number of outstanding requests
« Reply #1 on: August 23, 2007, 08:47:29 AM »
Hi Victor,

I've been using Platform SDK for more then 1 year and I didn't stumble on such limitation ( surely there is something ) but for normal agent desktop application it has hard to reach it. I'am working on some project where server application ( using Platform SDK ) will be processing a lot of request and events - if I will find some limitation I will post it


Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1416
  • Karma: 18
Re: Voice Platform:number of outstanding requests
« Reply #2 on: August 24, 2007, 01:48:13 AM »
This is a problem that I am currently trying to resolve.
I wrote an app that acts as a proxy server between Genesys T-Server and softphones.
We are talking about sending 100 requests per second here... not sure if it can handle it.


Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: Voice Platform:number of outstanding requests
« Reply #3 on: August 24, 2007, 11:12:42 AM »
Victor,

Did You tried to create pool of Protocol objects and load balance client's between them ? - new SDK luckily for us is thread safe. Protocol object inside pool can be selected based on DN number for which specific client registeres or base on client ip address

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1416
  • Karma: 18
Re: Voice Platform:number of outstanding requests
« Reply #4 on: September 03, 2007, 06:42:54 AM »
I was thinking about it, but was too lazy.
At the end, we did testing where we would have 10 to 15 messages per second and PBX flipped out on us after continuous login-requests. After about 250 request send at 100 ms interval, MAPD took more than 10 seconds to process it, so T-Server started to return timeout error.

I am hoping AES performs better than that. In a meantime, I don't want to write more than have to.

Best regards,
Vic