Will Genuine Channels be made obsolete by WCF

Hi,

We are currently designing the communication for our upcoming system
and recently found the Genuine Channels
(http://www.genuinechannels.com/) that seems to solve most of the
problems that are connected to our network infrastructure. Now we are
wondering whether WCF will implement the same feature set as GC. Is
this the case? Will WCF make GC obsolete?

Genuine Channels currently has the following feature set. Will WCF have
something similar?

* Bi-directional remoting
When implementing events/callbacks you only have to open up one
TCP-connection (from the client to the server). This connection will
then be reused whenever the server calls the client. This will really
simplify NAT:ing for our off-the-shelve application.

* Asynchronous calls
Both the client and the server can make asyncronous calls through the
single established TCP-connection. The framework handles all the
complicated details.

* Guaranteed call timeout
Each call can be made to throw an exception if takes longer than a
given threshold time.

* Channel monitoring
Both the client and the server is notified whenever their counterpart
is disconnected

* Compression
Can be enabled for separate calls or for all calls through the API.

* Broadcast engine
Asynchronous events that will be sent to several clients at the same
time.

We would be most greatfull for your information and opinion on these
matters.

Best Regards
//Jan Persson

Hi!

<jan.persson@gmail.com> wrote in message
news:1163433835.852985.312940@e3g2000cwe.googlegroups.com...
> Hi,
>
> We are currently designing the communication for our upcoming system
> and recently found the Genuine Channels
> (http://www.genuinechannels.com/) that seems to solve most of the
> problems that are connected to our network infrastructure. Now we are
> wondering whether WCF will implement the same feature set as GC. Is
> this the case? Will WCF make GC obsolete?
>
> Genuine Channels currently has the following feature set. Will WCF have
> something similar?
>
> * Bi-directional remoting
> When implementing events/callbacks you only have to open up one
> TCP-connection (from the client to the server). This connection will
> then be reused whenever the server calls the client. This will really
> simplify NAT:ing for our off-the-shelve application.
>
Dual binding ( for callback ) use separate channel to connect from service
to client
> * Asynchronous calls
> Both the client and the server can make asyncronous calls through the
> single established TCP-connection. The framework handles all the
> complicated details.
>
Yes, but be aware that async call from client , really the implementation
of client side WCF , service know nothing about it.

> * Guaranteed call timeout
> Each call can be made to throw an exception if takes longer than a
> given threshold time.
>
Yes

> * Channel monitoring
> Both the client and the server is notified whenever their counterpart
> is disconnected
Client notified on action when service gone, but not v.v directly
>
> * Compression
> Can be enabled for separate calls or for all calls through the API.
>
Yes, if you use custom binding

> * Broadcast engine
> Asynchronous events that will be sent to several clients at the same
> time.
>
No default UDP support in WCF, but exist example of builing UDP transport.
In advance you can use it for multicast ( no broadcast in IPv6 )
That's IMHO because communication is SOAP , so UDP not in use because of
being unreliable

Arkady

> We would be most greatfull for your information and opinion on these
> matters.
>
> Best Regards
> //Jan Persson
>

Hi,

Thank you. This helps us a lot.

Best Regards
//Jan Persson

Arkady Frenkel skrev:

> Hi!
>
> <jan.persson@gmail.com> wrote in message
> news:1163433835.852985.312940@e3g2000cwe.googlegroups.com...
> > Hi,
> >
> > We are currently designing the communication for our upcoming system
> > and recently found the Genuine Channels
> > (http://www.genuinechannels.com/) that seems to solve most of the
> > problems that are connected to our network infrastructure. Now we are
> > wondering whether WCF will implement the same feature set as GC. Is
> > this the case? Will WCF make GC obsolete?
> >
> > Genuine Channels currently has the following feature set. Will WCF have
> > something similar?
> >
> > * Bi-directional remoting
> > When implementing events/callbacks you only have to open up one
> > TCP-connection (from the client to the server). This connection will
> > then be reused whenever the server calls the client. This will really
> > simplify NAT:ing for our off-the-shelve application.
> >
> Dual binding ( for callback ) use separate channel to connect from service
> to client
> > * Asynchronous calls
> > Both the client and the server can make asyncronous calls through the
> > single established TCP-connection. The framework handles all the
> > complicated details.
> >
> Yes, but be aware that async call from client , really the implementation
> of client side WCF , service know nothing about it.
>
> > * Guaranteed call timeout
> > Each call can be made to throw an exception if takes longer than a
> > given threshold time.
> >
> Yes
>
> > * Channel monitoring
> > Both the client and the server is notified whenever their counterpart
> > is disconnected
> Client notified on action when service gone, but not v.v directly
> >
> > * Compression
> > Can be enabled for separate calls or for all calls through the API.
> >
> Yes, if you use custom binding
>
> > * Broadcast engine
> > Asynchronous events that will be sent to several clients at the same
> > time.
> >
> No default UDP support in WCF, but exist example of builing UDP transport.
> In advance you can use it for multicast ( no broadcast in IPv6 )
> That's IMHO because communication is SOAP , so UDP not in use because of
> being unreliable
>
> Arkady
>
> > We would be most greatfull for your information and opinion on these
> > matters.
> >
> > Best Regards
> > //Jan Persson
> >

As additional point be aware that WCF is communication platform for any (
all ) type of communications ( pipes, sockets, http , p2p .... ) opposite to
..Net Remoting ( as I see genuinechannels used ) which is limited subset of
WCF
Arkady


"Arkady Frenkel" <arkadyf@hotmailxdotx.com> wrote in message
news:Olutdh9BHHA.4680@TK2MSFTNGP04.phx.gbl...
> Hi!
>
> <jan.persson@gmail.com> wrote in message
> news:1163433835.852985.312940@e3g2000cwe.googlegroups.com...
>> Hi,
>>
>> We are currently designing the communication for our upcoming system
>> and recently found the Genuine Channels
>> (http://www.genuinechannels.com/) that seems to solve most of the
>> problems that are connected to our network infrastructure. Now we are
>> wondering whether WCF will implement the same feature set as GC. Is
>> this the case? Will WCF make GC obsolete?
>>
>> Genuine Channels currently has the following feature set. Will WCF have
>> something similar?
>>
>> * Bi-directional remoting
>> When implementing events/callbacks you only have to open up one
>> TCP-connection (from the client to the server). This connection will
>> then be reused whenever the server calls the client. This will really
>> simplify NAT:ing for our off-the-shelve application.
>>
> Dual binding ( for callback ) use separate channel to connect from
> service to client
>> * Asynchronous calls
>> Both the client and the server can make asyncronous calls through the
>> single established TCP-connection. The framework handles all the
>> complicated details.
>>
> Yes, but be aware that async call from client , really the implementation
> of client side WCF , service know nothing about it.
>
>> * Guaranteed call timeout
>> Each call can be made to throw an exception if takes longer than a
>> given threshold time.
>>
> Yes
>
>> * Channel monitoring
>> Both the client and the server is notified whenever their counterpart
>> is disconnected
> Client notified on action when service gone, but not v.v directly
>>
>> * Compression
>> Can be enabled for separate calls or for all calls through the API.
>>
> Yes, if you use custom binding
>
>> * Broadcast engine
>> Asynchronous events that will be sent to several clients at the same
>> time.
>>
> No default UDP support in WCF, but exist example of builing UDP transport.
> In advance you can use it for multicast ( no broadcast in IPv6 )
> That's IMHO because communication is SOAP , so UDP not in use because of
> being unreliable
>
> Arkady
>
>> We would be most greatfull for your information and opinion on these
>> matters.
>>
>> Best Regards
>> //Jan Persson
>>
>
>