Re: Web service with Push to client ?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Semedao,

WCF supports a P2P channel to expose services.
However, the client and the service both must use WCF, so I am not sure if
this is a good solution for you. If it is, you should take a look there.

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

"semedao" <semedao@xxxxxxxxxxxxxxxx> wrote in message
news:Ozt%23x0ruGHA.4952@xxxxxxxxxxxxxxxxxxxxxxx
Hi Steven,
I need this behavior for P2P applicaiton that should be able to work also
behind NAT
if you see this article:
http://www.brynosaurus.com/pub/net/p2pnat/
We need that when client X try to connect client Y and both behind NAT ,
they need server that notify them to try connect each one , so , if I want
to implement the server as WS , I need also the option to notify client Y
that client X try to connect him , and that he also need to try connect to
client X.
If WS don't let me do it (I have the connection details of both clients) ,
I will not be able to implement TCP hole punching via WS.
before I will decide to go to my own tcp server... there is still chance
to do something ? :)
thanks
"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:8oTF1bpuGHA.5988@xxxxxxxxxxxxxxxxxxxxxxxx
Hi Semedao,

I agree with Scott, from standard webservice's perspective, there is no
server-side push mechanims or callback interface. And XML webservice is a
public service which expose its functionliaty through the service
contract(WSDL document) and let various clients to consume it. The
webservice itself should not have any sense of the client consumer or
platform. However, if we want the webservice to actively push/ping
client
side, it will require our server-side service has sufficient information
about the client-side's programming interface and platform, this is
somewhat violating the webservice standard.

BTW, such server-side push(to multiple clients) is quite expense
especially
for internet scenario. Is the webservice in your scenario work in
intranet
or internet scenario? If convenient, you can provide us some further
background info so that we can look for some other solutions according to
your scenario.


Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no
rights.





.

Relevant Pages

  • RE: 404 Not Found
    ... Can a config file possibly tell it not to look in hte GAC? ... what's the current trustLevel of your ASP.NET webservice on the server ... >> whether it is client side related..... ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Webservice problem (after iisreset)
    ... I was speaking about whatever means you're suing the make the call from the client. ... If it already waits one minute for the failure then it sounds like the timeout is already high enough. ... So use wsdl.exe to generate a .NET proxy to your webservice to see if that style of client has the same problems or not. ... If it does, then it sounds like something on the server, if it does not then it's likley your HTC framework. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • Re: Web service testing
    ... To test if my code was faulty or not, I back-ported the web service to a standard 2.0 web service using Visual Studio 2005. ... The service is run under IIS on a Windows 2003 server, so there are no server side connection limits that can explain this. ... ASP.NET webservice application. ... In addition, since the problems occur at client, you can use Visual studio ...
    (microsoft.public.dotnet.framework.webservices)