[Tutor] suggestions for read unread items datastructure

[Luke Paireepinart]

anil maran wrote:
> i m sure the users need to maintain their own data,
> but as a provider we need to store their information
> right, sessions and cookies work only during their
> stay in the site, after they exit, im sure they would
> like to come back to the same info, wont u
>
> so i was wondering what is the best way to maintain
> the list of read/unread items in a python
> datastructure, 
>   
It's not that we don't want to help you, it's that we don't understand 
what you want to do.
Consider this:
Are you trying to make a client-side program for this?
    If so, why do you care about storing multiple user data?
Are you making a server that mirrors other RSS feeds for your users?
 
Are you making a client-side program that communicates with a single server
that has everyone's RSS feeds on it?

Why do you think you need to do things this way?
Why are you concerned about the data structure used to store this when 
there's
other things to be concerned about (RSS feed parsing, etc, etc.)
This should be one of the last things you worry about.

Also, Alan wasn't suggesting you use cookies.
He was stating that websites allow the client to maintain information 
about their own activities,
rather than the server trying to manage all the users.
He means that maybe you shouldn't be concerned about which RSS feeds 
your clients have been to
and let the clients take care of it themselves.

Sort of how my mailserver sends me all my mail, but my E-mail client 
takes care of marking
individual messages 'read/unread' and sorting it into folders.  There's 
no reason for the server
to need to know about any of this stuff.  Does your server really need 
to know about which
RSS feeds the clients have viewed?
> --- Alan Gauld <alan.gauld at freenet.co.uk> wrote:
>
>   
>> Caveat - I know nothing about RSS, it's one of those
>> web 
>> technologies that I just can't get excited about,
>> sorry...
>>
>> However...
>>
>>     
>>> there is a blog
>>> and it associated feed entries
>>> the blog posts
>>> when someone clicks it i need to maintain read
>>>       
>> status for it
>>     
>>> and when it is unclicked i need the unread status
>>> this needs to be maintianed for a huge number of
>>>       
>> usrs
>>
>> Whenever you need to maintain data for "a huge
>> number of users"
>> its time to question whether it's your job to
>> maintain the data. 
>> Maybe the users should each maintain their own data?
>> That's 
>> the idea behind cookies in a web browsing context -
>> does 
>> anything similar work for RSS?
>>
>> Alan G.
>>
>>     
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> http://mail.python.org/mailman/listinfo/tutor
>
>