Long story short; is Facebook web application or any other social network web app handling in two different ways the in-app notifications(through web socket) and the push notification(through service worker)?
Is this statement correct?
I'm developing a web platform (social network alike) and I'm looking for a smart way to handle notifications (push notification and in app notification), NOT displaying, which is quite straight forward.
To be more clear I mean "in-app notification" those appearing in the upper right corner of the web app (usually) and displayed with fancy js or whatever, and I mean "push notification" those showed by the browser through the Notification API based on Push API and service worker.
Related
I am currently working on an web application, which need to implement a notification system, just like Facebook and Youtube does. (Not mobile PUSH Notification. Just to show how many notifications are in the notification couter and, when soneone expand it, show all notifications. Just as Facebook) What I need to know is, what is the following best method to use.
1.Websocket
2.SSE
3 XMPP
Our application is on budget and, we are running it on a VPS server.
I need to implement live customer support chat to liferay 7.
Portal will provide capability for the end user to chat with the support users for online issue resolution, technical and non technical help. Portal support team can support the end users over chat as well over E-mail for the first tracking issue resolution. The user will be provided with a hyper link at footer of each page to start Web Chat. Once the user clicks on Web Chat the Web Chat window will be opened for communication. User can put his/her e-mail id, issue category and queries to start Web Chat. Once the Web Chat will be initiated by user, one chat window will be opened at for support user who is logged in mediation portal to provide support. If the support team is not available, then the end user will be communicated with a message that, Customer support teat will be in touch with you soon on e-mail. The user chat requests will be allocated among the support users those who are logged in mediation portal in round robin method.
There is the native chat portlet, but I really do not recommend using it for your case, your case is a bit more complex then what comes out of the box. You will be better served if a support system plugin.
I like https://www.zendesk.com/chat/
Which is pretty easy to install and customize.
It is possible to implement push notifications desktop (chrome or firefox) for each specific user application using https://github.com/developerdynamo/laravel-push-notification?
Sure. As long as you have a way sync with the client in the background, like a websocket connecion, you can easily use the Web Notification API.
I am going to integrate chat module in my application. It's a mobile application having front end in swift and backend in spring boot. So my chat module will have functionalities :)
1) There will be a one to one chat,not a group chat
2) i have to send push notification to user when user goes offline or app closed
3) i have to show online users list on user's dashboard
4) i have to store messages in database
5) User can send images,videos in chat
I know these functionalities are common in all modern mobile applications.
I am very new to messaging protocols,please suggest me a best protocol as well suited to my requirements.
Any advice will be helpful,Thanks
Take a look to the The Message Session Relay Protocol (MSRP)
You can find a comparison here.
I have been working on a web app that, among other things, allows users to communicate with each other using Google+ Hangout.
The web app initiates the hangout and passes the Hangout URL to other potential participants. During the Hangout sessions the Hangout app sends information back to the server (using Ajax) on several events such as “onParticipantsAdded", "onParticipantsRemoved" etc.
I am trying to find out a way to notify the web app when the Hangout is over. The other events I mentioned (such as onParticipantsRemoved) will not work once the last participant leaves.
Currently I am sending a “heartbeat” from the hangout to the web app every few minutes, but I am wondering if there is a better way to know when the Hangout ends?
Since the hangout operates inside a window, you might be able to catch the onclose event for that window, but best practice is to rely on a heartbeat, as you've described.