silverlight - backgroundworker process [modified]
-
With WCF you can retrieve data, etc into silverlight UI using asyncronous calls... Then is there any reason for backgrooundworker process to be used in silverlight? Thanks
modified on Thursday, September 1, 2011 1:28 AM
Define required! I am yet to use a BGW process in SL.
Never underestimate the power of human stupidity RAH
-
Define required! I am yet to use a BGW process in SL.
Never underestimate the power of human stupidity RAH
-
With WCF you can retrieve data, etc into silverlight UI using asyncronous calls... Then is there any reason for backgrooundworker process to be used in silverlight? Thanks
modified on Thursday, September 1, 2011 1:28 AM
I'm sure you've asked this question before. Yes, you can use a background worker to do something in Silverlight, but in most cases it's not necessary because of the asynchronous nature of the client/server roundtrip. Saying that, you could be attempting to do something entirely on the client side, e.g. performing a long running calculation, and you should use some form of threading for this. The answer you are looking for: Roundtrip = asynchronous = no need for additional threading Client side only = synchronous = you might want to use threading here.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
I'm sure you've asked this question before. Yes, you can use a background worker to do something in Silverlight, but in most cases it's not necessary because of the asynchronous nature of the client/server roundtrip. Saying that, you could be attempting to do something entirely on the client side, e.g. performing a long running calculation, and you should use some form of threading for this. The answer you are looking for: Roundtrip = asynchronous = no need for additional threading Client side only = synchronous = you might want to use threading here.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
In that case, on the client side, to use threading, I can use background worker? and not manually creating threads like thread t = new thread(...)? Thanks
arkiboys wrote:
on the client side, to use threading, I can use background worker
Yes.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
arkiboys wrote:
on the client side, to use threading, I can use background worker
Yes.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
I see. So in silverlight, I do not need to learn how to do manual threading as long as I know backgroundworker process? Thanks
That's correct. Learning manual threading is good knowledge to have, it will make you a better coder, but it isn't absolutely necessary.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
That's correct. Learning manual threading is good knowledge to have, it will make you a better coder, but it isn't absolutely necessary.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility