Re: Re[2]: email notification and abstract methods

On Nov 15, 2003, at 7:39 AM, nemilya wrote:

>>> Summary:
>>> 1. notification to user on new post in blog
>>> 2. notification to blog's author on comments to blog's record
>>> 3. notification to user on new comments in specified blog's record
>
> KS> I was actually only looking for number 2 on this list. That's very
> KS> simple and easy to do.
>
> How do you plan to do it?
>
How about just a method on XMLFormServlet, sendEmail(address, subject,  
message) and then call it when a comment or trackback is posted.

Basically I was just going to do the simplest possible thing that will  
work. If something more complex proves to be necessary later, then  
again a re-factoring can be done at that time.

> In simplest way, in Comment.py
> after
>   self.weblog.addPost(content, 0)
> add
>   self.notificator.notifyAuthor(postID)
> where
>   'notificator' class for tasks of notifications.
>
> Or add 'event/subscriber' architecture.
> in this case:
>   self.dispatcher.send( EventAddComment( postID ) )
>
> and in dispatcher there is matrix of subscibed objects.

>
> KS> You make a good point with the others, but I'm
> KS> not sure that email is the way to handle that. I had been toying  
> with
> KS> using RSS for it.
>
> Hm. I have email client but haven't any RSS clent.
> May be become time for RSS-grabber?ss

Yeah, weblogs and RSS go hand in hand. If you want to work on weblog  
software you have to use RSS.

>
> Or wxPython GUI application, for working with blogs, and for reading
> other?
>
I'm sure something like this exists. I personally use NetNewsWire on  
Mac OS X.

> or, consider next variant:
>
> Machine1 (Machine3, 4, ...)
> service: 'Blog' (some user's blog)
> out: rss
>
> Machine2
> service: 'RSS to Email notification, i.e. subscription'
> in: rss (access to Machine1, 3, 4, ...)
> out: email notifications to user by rules defined by users
>
That is certainly doable. It may already exist, probably does actually,  
but I don't know for sure.
> ?
>
> KS> It would be trivial to have a per post RSS feed for
> KS> the comments as well as a global feed for all comments. Using RSS  
> puts
> KS> control over subscriptions into the hands of the user without  
> having to
> KS> write a management UI.
>
> one problem, what software for working with rss exists?

Lots. http://www.hebig.org/blogs/archives/main/000877.php

>
> KS> It also means we don't have to store email
> KS> addresses. That may be preferable then having to deal with email.  
> In
> KS> reality we could just implement the RSS and not deal with email at  
> all,
> KS> but I think having notifications to the author is a good thing
> KS> (translation: it's something I personally want to use). :-)
>
> 'author' you mean blog's author?
>
Yes that's exactly what I mean.

> As I think only blog's author can post posts. Users only read posts,
> and posts comments.
>
> KS> So my feeling on this is RSS for user notifications and email on
> KS> trackbacks and comments for authors only, at least for right now.
>
> Please describe what is 'trackbacks'? (I'am novice in blog industry :))
>
Trackbacks are kind of like comments, but they just post an excerpt and  
then link back to a remote weblog post that contains the rest of the  
content. Read this, http://www.muhajabah.com/islamicblog/what-is-tb.htm

> KS> On Nov 14, 2003, at 11:19 PM, nemilya wrote:
>
>>> About story of sending email notification
>>>
>>> I think that for email notification have to be list of subscribed
>>> users. F.e. 'user-subscribe.xml', with 'id', 'email', 'activated')
>>> also possible for activation logic additional xml storage
>>> 'user-activation-code.xml' is needed:
>
> KS> The way you would do this in syncato is to add each user element  
> as a
> KS> separate database entry. id would be assigned by the system and  
> then
> KS> you can specify indexes on the rest.
>
> KS> Obviously this doesn't work as well for the file database as it  
> does
> KS> for DB XML.
>
> ok, this is news for me.
>
> But why is not allowed to add childs (user information entry) by DOM?
> Or xmldb have self rules?

It has nothing to do with having children in the document it's about  
not treating a document it self as a database. That's what you're doing  
when you have a whole sequence of similar nodes in a document like your  
example. DB XML indexes only help selection of documents from a set of  
documents, they don't help with selection within a single document. A  
loose analogy to the relational world is to consider collection = table  
and document = row. In Syncato there is only one collection and a whole  
bunch of documents.

>
> Ilya
>
>
>
>
> -------------------------------------------------------
> This SF. Net email is sponsored by: GoToMyPC
> GoToMyPC is the fast, easy and secure way to access your computer from
> any Web browser or wireless device. Click here to Try it Free!
> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/ 
> g22lp.tmpl
> _______________________________________________
> Syncato-general mailing list
> Syncato-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/syncato-general
>
>
Kimbro Staken
Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl