Showing posts with label protocol. Show all posts
Showing posts with label protocol. Show all posts

Sunday, February 19, 2012

How to send Notifications to WinForm?

How to send Notifications to WinForm?

How to define the user devices and the custom delivery protocol and delivery channel?

Can you give me some examples? Source Codes?

Thank you very much!

no replies!

|||There are a number of ways you could do this, but it really depends on what you're trying to accomplish. You could deliver through MSMQ and poll the queue with your WinForms app, or you could probably even create a remoting delivery protocol. It'd probably help if you explained what you're really trying to accomplish.|||

How to create a remoting delivery protocol? The WinForm and the NS are on two different matchines.

Thank you very much!

|||

It's not something I've done, so I can't cut and paste code for you. I imagine a good start would be:

Developing a Custom Delivery Protocol

and a good tutorial on remoting. If you have access to it, or are willing to buy it, Ingo Rammer's Advanced .NET Remoting is probably the book to get.

-Francis

How to send notification to .aspx page...

... as far as I understand, I need to create a custom HTTP protocol. Where do get an example of this? Shyam's book has an example of creating custom protocol that is not HTTP based. There are few remarks on HTTP custom protocol in Chapter 10, but those are not very helpful.

The scenario it is used for is as follows: ASP.NET messenger (an .aspx page) writes messages into SQL server table. The page needs to get notified as soon as new entry appears in the table (from another instance of messenger), so that the first instance of messenger would be able to get new message from the table. Is this appropriate usage of notification services? If not, can you suggest alternative ways to write ASP.NET messenger?

Thank you in advance.

Is this a kinda IM application ? If so NS is not a right choice for Real Time Communication I would prefer to explore RTC (Real Time CommunicationI API with MS Live Communication Server. These two works well for any IM/Messaging related application.

If you mention ur requirements in detail (what do u mean by message etc) i will be more clear... thanks

--Satyen

|||

Query Notifications may be a better technology choice for you in this application.

HTH...

Joe

How to send notification to .aspx page...

... as far as I understand, I need to create a custom HTTP protocol. Where do get an example of this? Shyam's book has an example of creating custom protocol that is not HTTP based. There are few remarks on HTTP custom protocol in Chapter 10, but those are not very helpful.

The scenario it is used for is as follows: ASP.NET messenger (an .aspx page) writes messages into SQL server table. The page needs to get notified as soon as new entry appears in the table (from another instance of messenger), so that the first instance of messenger would be able to get new message from the table. Is this appropriate usage of notification services? If not, can you suggest alternative ways to write ASP.NET messenger?

Thank you in advance.

Is this a kinda IM application ? If so NS is not a right choice for Real Time Communication I would prefer to explore RTC (Real Time CommunicationI API with MS Live Communication Server. These two works well for any IM/Messaging related application.

If you mention ur requirements in detail (what do u mean by message etc) i will be more clear... thanks

--Satyen

|||

Query Notifications may be a better technology choice for you in this application.

HTH...

Joe

How to send notification to .aspx page...

... as far as I understand, I need to create a custom HTTP protocol. Where do get an example of this? Shyam's book has an example of creating custom protocol that is not HTTP based. There are few remarks on HTTP custom protocol in Chapter 10, but those are not very helpful.

The scenario it is used for is as follows: ASP.NET messenger (an .aspx page) writes messages into SQL server table. The page needs to get notified as soon as new entry appears in the table (from another instance of messenger), so that the first instance of messenger would be able to get new message from the table. Is this appropriate usage of notification services? If not, can you suggest alternative ways to write ASP.NET messenger?

Thank you in advance.

Is this a kinda IM application ? If so NS is not a right choice for Real Time Communication I would prefer to explore RTC (Real Time CommunicationI API with MS Live Communication Server. These two works well for any IM/Messaging related application.

If you mention ur requirements in detail (what do u mean by message etc) i will be more clear... thanks

--Satyen

|||

Query Notifications may be a better technology choice for you in this application.

HTH...

Joe