Dac

[tifosi]

My imagination or does it look like they've fixed the multi thread issues?

Forcing single-connection-at-a-time to DAC will really level the playing field... for a while.

S

 

[danny]

Hi,

Can you explain what you mean by 'multithread issues'? and 'what single connection-at-a-time' is?

Sorry for being a bit thick but i'm sure i'm not the only one out there that is naive of tech talk.

Cheers mate

 

[philipp]

Hi,
Can you explain what you mean by 'multithread issues'? and 'what single connection-at-a-time' is?

Sorry for being a bit thick but i'm sure i'm not the only one out there that is naive of tech talk.

The DAC was apparently allowing multiple connections from the same IP address, that's now been fixed.

You'll find lots about multithreading on the web; essentially, it's a form of light-weight multi-tasking, where an application can have multiple threads of execution which appear to run independantly from each other. On some hardware threads can run with true concurrency too, meaning that the job gets done faster.

This is as opposed to having multiple processes which have greater overheads and are thus more expensive in terms of computing resources.

You wouldn't really want an application like the DAC server to create a new process to service each connection as it would just tie up the system, so they've taken a multi-threaded approach with presumably a single thread per each connection. It's just more efficient that way.

A drawback is that it can be a bit fiddly programming threaded applications and speaking from experience, it's easy to introduce bugs.

Sorry, this has become quite a ramble!

Regards,

P.

 

[netserve]

Wouldn't know to be honest as our system only ever uses one thread.

 

[tifosi]

The DAC officially moved to a single connection version today.

Time will tell if this will level the playing field and stop the monopoly that has been going on for the past few months.

S

 

[netserve]

Not sure how this will level the playing field to be fair.

The limits on the number of queries to the dac still appeared to stand even when two or more connections could be established so having 5 connections to dac doesn't appear on the face of it to benefit anyone, or have I missed something?