"Steve" <lnuxguy_NOMAIL_PLEASE_@gmail.com> wrote in message
news:OItmgKl6HHA.4348@TK2MSFTNGP06.phx.gbl...
> When tp.ReturnCSRRequests finishes executing, its thread is killed.
>
>
> Steve C.
> MCSD,MCAD,MCSE,MCP+I,CNE,CNA,CCNA
>
>
> Roger wrote:
>> I have a windows service (I know, wrong group but I couldn't find a
>> windows service group) loads an individual record from a db to do some
>> work.
>> I use a thread to do this because it is possible for a large number of
>> requests to come through at the same, or close to the same time. Part of
>> the function involves me updating a clients database via a web-service.
>> Since this can be slow at times I don't want to serialize the requests,
>> hence the threads.
>>
>> The threading seems to work fine. The processes 'spin off' and run
>> concurrently. I don't ever 'kill' the thread. How does it know when to
>> end/turn itself off? I assume it does... but I'd hate to get really busy
>> and find out I was wrong...
>>
>> Thanks.
>>
>> I do my threading like this:
>>
>> tp = New ThreadedProcessor
>> thisThread = New Thread(AddressOf tp.ReturnCSRRequests)
>> thisThread.Start()

Roger wrote:
> Thank you.
>
> BTW: Do you have time to work with taking all those courses??? You've got a
> whole alphabet there!
>
>
> "Steve" <lnuxguy_NOMAIL_PLEASE_@gmail.com> wrote in message
> news:OItmgKl6HHA.4348@TK2MSFTNGP06.phx.gbl...
>> When tp.ReturnCSRRequests finishes executing, its thread is killed.
>>
>>
>> Steve C.
>> MCSD,MCAD,MCSE,MCP+I,CNE,CNA,CCNA
>>
>>
>> Roger wrote:
>>> I have a windows service (I know, wrong group but I couldn't find a
>>> windows service group) loads an individual record from a db to do some
>>> work.
>>> I use a thread to do this because it is possible for a large number of
>>> requests to come through at the same, or close to the same time. Part of
>>> the function involves me updating a clients database via a web-service.
>>> Since this can be slow at times I don't want to serialize the requests,
>>> hence the threads.
>>>
>>> The threading seems to work fine. The processes 'spin off' and run
>>> concurrently. I don't ever 'kill' the thread. How does it know when to
>>> end/turn itself off? I assume it does... but I'd hate to get really busy
>>> and find out I was wrong...
>>>
>>> Thanks.
>>>
>>> I do my threading like this:
>>>
>>> tp = New ThreadedProcessor
>>> thisThread = New Thread(AddressOf tp.ReturnCSRRequests)
>>> thisThread.Start()
>
>