WPF Threading Model

[Yehia A.Salam]

Hello,

I am building a network application that make use of .Net Sockets, I created
a class that works like a server and fires an event when anything arrives at
the server, however I ran into some problems because of the WPF threading
model, my code is like:

//*************** *************** *************
public Window1(){ ...
sConnection = new myserver();
sConnection.Dat eReceived += new
myserver.DataRe ceivedHandler(O nServerDataRece ived);
sConnection.Sta rtServer();
}

private void OnServerDataRec eived(MessageTe xt Re) {
Dispatcher.Begi nInvoke(System. Windows.Threadi ng.DispatcherPr iority.Normal,
new myserver.DataRe ceivedHandler(t his.ServerDataR eceived),Re);

}

private void ServerDataRecei ved(MessageText Re) {
txtconsole.Text = txtconsole.Text + Re.name + ": " + Re.content;
}
//*************** *************** *************** *

the code runs correctly but I am not satisfied with the structure, I don't
like that I must have at least two methods for modifying anything in the UI,
is there a better structure to do this, like putting BeginInvoke in myServer
Class for example and just assign the ServerDataRecei ved event in Window1
class like I would normally do in Windows Forms.

Thanks
Yehia A.Salam

[Nicholas Paldino [.NET/C# MVP]]

Yehia,

Well, personally, you are taking on a good deal of typing overhead which
I don't feel you have to do. First, you don't have to declare the delegate
constructor when you assign event handlers, like so:

sConnection.Dat eReceived += OnServerDataRec eived;

Also, you can declare your OnServerDataRec ieved like so:

private void OnServerDataRec eived(MessageTe xt Re)
{
myserver.DataRe ceivedHandler handler =
delegate(Messag eText mt)
{
txtconsole.Text = txtconsole.Text + mt.name + ": " + mt.content;
};

Dispatcher.Begi nInvoke(System. Windows.Threadi ng.DispatcherPr iority.Normal,
handler, Re);
}

This way, you don't need to have another handler. Granted, the same
amount of jumps are made (the anonymous delegate creates a method on your
class underneath the covers which is really assigned to the delegate), but
you have consolidated the code somewhat.

However, if you need to reuse that code (the ServerDataRecei ved method)
and using an anonymous delegate only leads to code duplication, then what
you have is the best way to handle it (and code it, with the exception of
declaring the delegate types).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:8F******** *************** ***********@mic rosoft.com...

Hello,

I am building a network application that make use of .Net Sockets, I
created a class that works like a server and fires an event when anything
arrives at the server, however I ran into some problems because of the WPF
threading model, my code is like:

//*************** *************** *************
public Window1(){ ...
sConnection = new myserver();
sConnection.Dat eReceived += new
myserver.DataRe ceivedHandler(O nServerDataRece ived);
sConnection.Sta rtServer();
}

private void OnServerDataRec eived(MessageTe xt Re) {
Dispatcher.Begi nInvoke(System. Windows.Threadi ng.DispatcherPr iority.Normal,
new myserver.DataRe ceivedHandler(t his.ServerDataR eceived),Re);

}

private void ServerDataRecei ved(MessageText Re) {
txtconsole.Text = txtconsole.Text + Re.name + ": " + Re.content;
}
//*************** *************** *************** *

the code runs correctly but I am not satisfied with the structure, I don't
like that I must have at least two methods for modifying anything in the
UI, is there a better structure to do this, like putting BeginInvoke in
myServer Class for example and just assign the ServerDataRecei ved event in
Window1 class like I would normally do in Windows Forms.

Thanks
Yehia A.Salam

[Willy Denoyette [MVP]]

"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:8F******** *************** ***********@mic rosoft.com...

Hello,

I am building a network application that make use of .Net Sockets, I
created a class that works like a server and fires an event when anything
arrives at the server, however I ran into some problems because of the WPF
threading model, my code is like:

//*************** *************** *************
public Window1(){ ...
sConnection = new myserver();
sConnection.Dat eReceived += new
myserver.DataRe ceivedHandler(O nServerDataRece ived);
sConnection.Sta rtServer();
}

private void OnServerDataRec eived(MessageTe xt Re) {
Dispatcher.Begi nInvoke(System. Windows.Threadi ng.DispatcherPr iority.Normal,
new myserver.DataRe ceivedHandler(t his.ServerDataR eceived),Re);

}

private void ServerDataRecei ved(MessageText Re) {
txtconsole.Text = txtconsole.Text + Re.name + ": " + Re.content;
}
//*************** *************** *************** *

the code runs correctly but I am not satisfied with the structure, I don't
like that I must have at least two methods for modifying anything in the
UI, is there a better structure to do this, like putting BeginInvoke in
myServer Class for example and just assign the ServerDataRecei ved event in
Window1 class like I would normally do in Windows Forms.

Thanks
Yehia A.Salam

Using an anon. delegate...

Dispatcher.Begi nInvoke(Dispatc herPriority.Nor mal,
(EventHandler)d elegate
{
txtconsole.Text = txtconsole.Text + Re.name + ":
" + Re.content;

}, Re);

Willy.

[Yehia A.Salam]

is that my only solution, can I solve this at the server class level?

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c omwrote in
message news:#f******** ******@TK2MSFTN GP03.phx.gbl...

Yehia,

Well, personally, you are taking on a good deal of typing overhead
which I don't feel you have to do. First, you don't have to declare the
delegate constructor when you assign event handlers, like so:

sConnection.Dat eReceived += OnServerDataRec eived;

Also, you can declare your OnServerDataRec ieved like so:

private void OnServerDataRec eived(MessageTe xt Re)
{
myserver.DataRe ceivedHandler handler =
delegate(Messag eText mt)
{
txtconsole.Text = txtconsole.Text + mt.name + ": " +
mt.content;
};
Dispatcher.Begi nInvoke(System. Windows.Threadi ng.DispatcherPr iority.Normal,
handler, Re);
}

This way, you don't need to have another handler. Granted, the same
amount of jumps are made (the anonymous delegate creates a method on your
class underneath the covers which is really assigned to the delegate), but
you have consolidated the code somewhat.

However, if you need to reuse that code (the ServerDataRecei ved method)
and using an anonymous delegate only leads to code duplication, then what
you have is the best way to handle it (and code it, with the exception of
declaring the delegate types).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:8F******** *************** ***********@mic rosoft.com...

>Hello,

I am building a network application that make use of .Net Sockets, I
created a class that works like a server and fires an event when anything
arrives at the server, however I ran into some problems because of the
WPF threading model, my code is like:

//*************** *************** *************
public Window1(){ ...
sConnection = new myserver();
sConnection.Da teReceived += new
myserver.DataR eceivedHandler( OnServerDataRec eived);
sConnection.St artServer();
}

private void OnServerDataRec eived(MessageTe xt Re) {
Dispatcher.Beg inInvoke(System .Windows.Thread ing.DispatcherP riority.Normal,
new myserver.DataRe ceivedHandler(t his.ServerDataR eceived),Re);

}

private void ServerDataRecei ved(MessageText Re) {
txtconsole.Text = txtconsole.Text + Re.name + ": " + Re.content;
}
//*************** *************** *************** *

the code runs correctly but I am not satisfied with the structure, I
don't like that I must have at least two methods for modifying anything
in the UI, is there a better structure to do this, like putting
BeginInvoke in myServer Class for example and just assign the
ServerDataRece ived event in Window1 class like I would normally do in
Windows Forms.

Thanks
Yehia A.Salam

[Nicholas Paldino [.NET/C# MVP]]

Yehia,

There is nothing you can do at the server level. As far as the server
is concerned, it gets a request and responds to it, it cares nothing (nor
should it, or could it) care about what thread the client called on in it's
app domain.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:32******** *************** ***********@mic rosoft.com...

is that my only solution, can I solve this at the server class level?

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c omwrote
in message news:#f******** ******@TK2MSFTN GP03.phx.gbl...

>Yehia,

Well, personally, you are taking on a good deal of typing overhead
which I don't feel you have to do. First, you don't have to declare the
delegate constructor when you assign event handlers, like so:

sConnection.Da teReceived += OnServerDataRec eived;

Also, you can declare your OnServerDataRec ieved like so:

private void OnServerDataRec eived(MessageTe xt Re)
{
myserver.DataRe ceivedHandler handler =
delegate(Messag eText mt)
{
txtconsole.Text = txtconsole.Text + mt.name + ": " +
mt.content;
};
Dispatcher.Beg inInvoke(System .Windows.Thread ing.DispatcherP riority.Normal,
handler, Re);
}

This way, you don't need to have another handler. Granted, the same
amount of jumps are made (the anonymous delegate creates a method on your
class underneath the covers which is really assigned to the delegate),
but you have consolidated the code somewhat.

However, if you need to reuse that code (the ServerDataRecei ved
method) and using an anonymous delegate only leads to code duplication,
then what you have is the best way to handle it (and code it, with the
exception of declaring the delegate types).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:8F******* *************** ************@mi crosoft.com...

>>Hello,

I am building a network application that make use of .Net Sockets, I
created a class that works like a server and fires an event when
anything arrives at the server, however I ran into some problems because
of the WPF threading model, my code is like:

//*************** *************** *************
public Window1(){ ...
sConnection = new myserver();
sConnection.D ateReceived += new
myserver.Data ReceivedHandler (OnServerDataRe ceived);
sConnection.S tartServer();
}

private void OnServerDataRec eived(MessageTe xt Re) {
Dispatcher.Be ginInvoke(Syste m.Windows.Threa ding.Dispatcher Priority.Normal ,
new myserver.DataRe ceivedHandler(t his.ServerDataR eceived),Re);

}

private void ServerDataRecei ved(MessageText Re) {
txtconsole.Text = txtconsole.Text + Re.name + ": " + Re.content;
}
//*************** *************** *************** *

the code runs correctly but I am not satisfied with the structure, I
don't like that I must have at least two methods for modifying anything
in the UI, is there a better structure to do this, like putting
BeginInvoke in myServer Class for example and just assign the
ServerDataRec eived event in Window1 class like I would normally do in
Windows Forms.

Thanks
Yehia A.Salam

[Yehia A.Salam]

ok will do that, Thanks a lot

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c omwrote in
message news:#X******** ******@TK2MSFTN GP04.phx.gbl...

Yehia,

There is nothing you can do at the server level. As far as the server
is concerned, it gets a request and responds to it, it cares nothing (nor
should it, or could it) care about what thread the client called on in
it's app domain.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:32******** *************** ***********@mic rosoft.com...

>is that my only solution, can I solve this at the server class level?

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c omwrote
in message news:#f******** ******@TK2MSFTN GP03.phx.gbl...

>>Yehia,

Well, personally, you are taking on a good deal of typing overhead
which I don't feel you have to do. First, you don't have to declare the
delegate constructor when you assign event handlers, like so:

sConnection.D ateReceived += OnServerDataRec eived;

Also, you can declare your OnServerDataRec ieved like so:

private void OnServerDataRec eived(MessageTe xt Re)
{
myserver.DataRe ceivedHandler handler =
delegate(Messag eText mt)
{
txtconsole.Text = txtconsole.Text + mt.name + ": " +
mt.content;
};
Dispatcher.Be ginInvoke(Syste m.Windows.Threa ding.Dispatcher Priority.Normal ,
handler, Re);
}

This way, you don't need to have another handler. Granted, the same
amount of jumps are made (the anonymous delegate creates a method on
your class underneath the covers which is really assigned to the
delegate), but you have consolidated the code somewhat.

However, if you need to reuse that code (the ServerDataRecei ved
method) and using an anonymous delegate only leads to code duplication,
then what you have is the best way to handle it (and code it, with the
exception of declaring the delegate types).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Yehia A.Salam" <ye*****@hotmai l.comwrote in message
news:8F****** *************** *************@m icrosoft.com...
Hello,

I am building a network application that make use of .Net Sockets, I
created a class that works like a server and fires an event when
anything arrives at the server, however I ran into some problems
because of the WPF threading model, my code is like:

//*************** *************** *************
public Window1(){ ...
sConnectio n = new myserver();
sConnection. DateReceived += new
myserver.Dat aReceivedHandle r(OnServerDataR eceived);
sConnection. StartServer();
}

private void OnServerDataRec eived(MessageTe xt Re) {
Dispatcher.B eginInvoke(Syst em.Windows.Thre ading.Dispatche rPriority.Norma l,
new myserver.DataRe ceivedHandler(t his.ServerDataR eceived),Re);

}

private void ServerDataRecei ved(MessageText Re) {
txtconsole.Text = txtconsole.Text + Re.name + ": " + Re.content;
}
//*************** *************** *************** *

the code runs correctly but I am not satisfied with the structure, I
don't like that I must have at least two methods for modifying anything
in the UI, is there a better structure to do this, like putting
BeginInvok e in myServer Class for example and just assign the
ServerDataRe ceived event in Window1 class like I would normally do in
Windows Forms.

Thanks
Yehia A.Salam