Problem with TCP request queing Feature

Hi Everybody.

I will have to implement Ticket buying system and I try to use TCP request queing to minimize user reject and prevent overwhelming connection on server. But I experience some issue.

Assume we have 10 connection limit and we have 100 user. And user need to open 2-3 connection before he can access web.

When start, user1-10 can open first 10 connection and F5 mark connection limit and send connection from user11-100 to queue.

The problem is when user1-10 want to open additional connection. Their second connection will be send to queue (after user11-100) and the result is user1-10 have slow and timeout while user 11-100 can't access to vs because connection limit is reached.

Did this feature can use to help us with Ticket buying system?

If it can, Can we reserve connection for user1-10 (who acess first) and additional connection from user1-10 have priviledge to access VS by not go to queue.

Thank you.