Re: Push like notifications app

Thanks for that.

I guess with these two examples they're building blocks to build an admin announcements service rather than a complete app itself - we'd still create the 'annoucement' app containing the message, expiry, 'who to' and so on - and these apps would handle the distribution.

I admit to glossing over the 'django-notifications' app having previously used 'django-notification' - which is completely different!

Guy

On Sunday, 17 August 2014 16:57:04 UTC+2, Cal Leeming [iops.io] wrote:

That was strange, my email decided to send as I was typing the rest of my reply :X See in-line again.

On Sun, Aug 17, 2014 at 3:53 PM, Cal Leeming [iops.io] <c...@iops.io> wrote:

Cal

On Sun, Aug 17, 2014 at 1:07 PM, Guy Bowden <guy.b...@gmail.com> wrote:

Hi,

I'm looking for an app that will allow me to 'push' notifications/messages to a user / users / groups via the admin system.

 

These might be useful;

https://github.com/django-notifications/django-notifications

https://github.com/justquick/django-activity-stream

It's also worth mentioning that I found that by searching for "django notifications" in Google, did you already check these out?

 

examples:

show all users a notice about a new feature

show users a notice about planned maintenance

and other such useful things!

it would be able to have a 'dismiss'/'delete' notification feature. Plus read/unread and so on.

Admin would enter the admin site, add in a new notice, select who should see it, perhaps with optional publish / unpublish dates and a level (info/warning/danger etc)

On the front end a templatetag would be used to fetch all notices to display, and then display them, marking them as read when they're displayed. There would be a simple way to dismiss a message and never see it again.

Anything like that exist? Seems fairly simple to create (don't they all!) if not.

Really depends on your use case.

If you're talking about less than 100k notifications in the life time of the application, and a throughput of under 10 reqs/sec, then you might get away with storing in your relational DB.

However if you're looking for a high throughput messaging system, multiple delivery channels, or large amounts of notifications, then you'd probably want to look into using something like Redis (or RabbitMQ), or perhaps *insert NoSQL technology here*.

 

Cheers

Guy 

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/29b03086-4b57-49bd-acda-36c78ddd19f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a6576c40-1a69-4090-b165-b07fdc1faddd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.