Remy Lebeau (TeamB) wrote:
> "Martin James" <nospam@dsl.pipex.com> wrote in message
> news:4582bb0a$1@newsgroups.borland.com...
>
>> Well, since the OnExecute event is run by the thread, you can call
>> the GetCurrentThread API in the event to get a handle to the thread
>> and change its priority.
>
> That would be very inefficient, as OnExecute is triggered in a loop for each
> connection.
A 'priorityAlreadyChanged' flag in the socket context - no problem.
Perhaps I should have explained that calling an expensive API on each
loop should be avoided!
Also, like you said, a connection could jump from one thread to
> another. And worse, if you use fibers, then you can have multiple
> connections running on a single thread.
..and you have no idea which thread it's going to be.
Rgds,
Martin
