Jump to content

Recommended Posts

So on my spare time, I am architecting a PHP service oriented application, which uses web services.

 

I want to architect a solution for delivering global, service, and user specific messages in the application. These type of messages would appear to the client after they have logged in. They would obviously be maintained at a database level but I need to build some pretty little php classes that can grab the data and display it in my application to the client if messages exist.

 

Is there a name for something like this? I am struggling on how to best design this solution so it is flexible and it would be nice to gain perspective on this topic. I just don't know what to look for and often times my results are related to designing a message system where clients of an application can communicate to each other, which is what I am NOT looking for.

Link to comment
https://forums.phpfreaks.com/topic/271224-application-message-solution/
Share on other sites

Are you talking about a message queue here? If so, then there's plenty of examples on how to construct one. A search online for "message queue" should net you a whole lot of examples, and you might even add the language of your choice to the search to get even more specific resources.

Maybe... It would need someone to administer the messages for application and application services. This admin could push the messages out and my application would listen for messages and show them to the client who is signed into the application (for application messages). The service that the client would have actively open in their browser would know to get messages based on the service. I would want this setup so messages would go away when the client selects a close button next to the message in the ui (maybe it makes an ajax request and updates the db to not show the message for that user anymore). Some messages might be more user specific and only appear based on the actions they have taken within the application they are using. These sort of messages wouldn't really need much administration. For example, maybe there would be a message telling newly signed up users to register their display name because this process wasn't required during registration.

 

So maybe this whole thing is a custom solution that I have to completely build myself rather than using a message cue and some custom code in my application? I still don't feel like I am getting a clear idea looking at message cues but perhaps they would be useful for application and application service messages meant to go to the client.

Edited by garbagedigger
This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.