Roger Sterling wrote:When desktop client starts, have it register a callback with the server.
For an example, is this no different than Microsoft Exchange server telling Microsoft Outlook that new mail has arrived in the user's mailbox ?
Saurabh Pillai wrote:
Roger Sterling wrote:When desktop client starts, have it register a callback with the server.
For an example, is this no different than Microsoft Exchange server telling Microsoft Outlook that new mail has arrived in the user's mailbox ?
In my case client is in C# and server is in Java (Spring framework). How do I implement "call back" functionality?
Ulf Dittmer wrote:Callbacks won't work in all cases, though - if the client's IP is NAT'ed somewhere along the way, all bets are off. Even if there's a unique IP, the firewall likely won't allow incoming connections.
Unless there's a persistent connection, of course, but if that's feasible depends on how many clients you expect. And since you're calling it "push notification", I'm guessing that you don't want one.
Ulf Dittmer wrote:Callbacks won't work in all cases, though - if the client's IP is NAT'ed somewhere along the way, all bets are off. Even if there's a unique IP, the firewall likely won't allow incoming connections.
Unless there's a persistent connection, of course, but if that's feasible depends on how many clients you expect. And since you're calling it "push notification", I'm guessing that you don't want one.
Ulf Dittmer wrote:I doubt the sys admins will be happy to change firewall settings just so such a scheme would work, and justifiably so IMO. It seems more realistic to constrain it to inside of the firewall, and possibly implement an additional pull option if it needs to work outside of it as well.
Saurabh Pillai wrote:
Ulf Dittmer wrote:Callbacks won't work in all cases, though - if the client's IP is NAT'ed somewhere along the way, all bets are off. Even if there's a unique IP, the firewall likely won't allow incoming connections.
Unless there's a persistent connection, of course, but if that's feasible depends on how many clients you expect. And since you're calling it "push notification", I'm guessing that you don't want one.
This is what my application is. We have a desktop app written in C# (Somebody else manages it. I work on server side which is Java(Spring Framework)). Desktop program is a Player which plays the playlist (list of images and videos). Desktop app calls the server to down the playlist through web service. All is fine so far. Now if somebody changes the playlist contents, server needs to send the notification to the player that contents has changed and please update your playlist. So client calls the server again and update the playlist (by downloading the new contents). This is the full cycle. The problem is how does server inform the client?
And my company is planning to sell the player as a product so we won't have access to customer's WIFI router, obviously. I am wondering how does any web chat works (like gmail chat)? It works on any network and it pushes the message to all devices which have gmail talk open like browser or phone.
Thank you for your time.
Ulf Dittmer wrote:You haven't said why it's so important that clients be notified right when new files are available, though, as opposed to a minute or so later, when a client-poll solution could reasonable be expected to learn about it.
Saurabh Pillai wrote:Now assume that we have 100 clients running, they would be calling server every minute in case of poll.
Climb the rope! CLIMB THE ROPE! You too tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|