writing multithread applications in dotnet 2.0?

  • Thread starter Thread starter Elhanan
  • Start date Start date
E

Elhanan

hi..

we are planning to do a file distibution system in dotnet 2.0 (the
system will recieve request for file transfers from one legacy system
to another using connect direct api, the execution of the file transfer
itself will be multi-threaded.

are there any differences between 1.1 and 2.0 in regards to 2.0?

we were thinking about placing the thing in a windows service, are
there any do's and don'ts in windows service i'll need to know about
(database access, multi-threads etc..)?
 
Hello, Elhanan!

E> we are planning to do a file distibution system in dotnet 2.0 (the
E> system will recieve request for file transfers from one legacy system
E> to another using connect direct api, the execution of the file transfer
E> itself will be multi-threaded.

E> are there any differences between 1.1 and 2.0 in regards to 2.0?
In what aspect of 2.0 you're interested? 1.1 and 2.0 have a lot of differences...

E> we were thinking about placing the thing in a windows service, are
E> there any do's and don'ts in windows service i'll need to know about
E> (database access, multi-threads etc..)?

It depends what you want to do, from with windows service. Regarding,
"(database access, multi-threads etc..)" there no limitations.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com
 
Hello Elhanan,

E> we are planning to do a file distibution system in dotnet 2.0 (the
E> system will recieve request for file transfers from one legacy system
E> to another using connect direct api, the execution of the file
E> transfer itself will be multi-threaded.
E> are there any differences between 1.1 and 2.0 in regards to 2.0?

take 2.0, cuz it has more extended functionality then 1.1

E> we were thinking about placing the thing in a windows service, are
E> there any do's and don'ts in windows service i'll need to know about
E> (database access, multi-threads etc..)?

take into account that services works in separate context, they starts before
user login (no ui interactions) and system account uder
service starts might have no access to the network


---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
i'm interested in aspects of multithreading functions, are there any
improvments. (java threading seems easier..)

can i actually use update delete databases from within a windows
service? i've heard that all services leave under the same memory
context any taxing one with intensive work might create a problem for
all.
 
Elhanan said:
i'm interested in aspects of multithreading functions, are there any
improvments. (java threading seems easier..)
Click to expand...

In what way is Java threading easier? .NET threading is pretty much the
same as Java threading in many respects, except that to my mind
delegates make .NET somewhat easier. Java 5 provides more utilities for
threading, but the basics are pretty much the same.
can i actually use update delete databases from within a windows
service?
Absolutely.

i've heard that all services leave under the same memory
context any taxing one with intensive work might create a problem for
all.
Click to expand...

No, services each run under their own process. Of course, any CPU time
you use in one service isn't available to the others - but that's true
of any process.
 
Back
Top