convore.json/groups/django-community/cross-session-storage-wo-db-backend/messages.json

[{"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667324.604286, "message": "Most certainly explaining what I'm looking for very poorly", "group_id": 81, "id": 96764}, {"user_id": 1, "stars": [{"date_created": 1297667765.543715, "user_id": 41}, {"date_created": 1297713894.634088, "user_id": 7381}], "topic_id": 5155, "date_created": 1297667756.9712591, "message": "Redis is the bees knees, we use it all over the place on Convore", "group_id": 81, "id": 96800}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667549.799346, "message": "@jsoncorwin Why don't you want to store that in the db?", "group_id": 81, "id": 96779}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667556.9340391, "message": "Too slow?", "group_id": 81, "id": 96780}, {"user_id": 7, "stars": [], "topic_id": 5155, "date_created": 1297667283.596524, "message": "I'm not sure I understand the question, and I'm almost certain you're pursuing a lost ause", "group_id": 81, "id": 96762}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667232.2008359, "message": "I'm interested in creating a global variable of sorts (sort of like what's stored in request.session, but cross session) without having to store data in the DB - is there anything like this?", "group_id": 81, "id": 96758}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667470.6369619, "message": "Or do you want to store the data in-process?", "group_id": 81, "id": 96772}, {"user_id": 7, "stars": [], "topic_id": 5155, "date_created": 1297667487.146616, "message": "in process is a bad idea", "group_id": 81, "id": 96773}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667499.132515, "message": "@alex I agree, I was just trying to get to the root of the question.", "group_id": 81, "id": 96776}, {"user_id": 1, "stars": [{"date_created": 1297713874.423214, "user_id": 7381}], "topic_id": 5155, "date_created": 1297667581.387486, "message": "I'd probably reach for Redis for that task, TBH", "group_id": 81, "id": 96782}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667592.730531, "message": "I think Redis is ideal", "group_id": 81, "id": 96784}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667644.072875, "message": "didn't know if that was a poor approach though", "group_id": 81, "id": 96788}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667692.4447441, "message": "i suppose that's what models are for - making table creation easy =p", "group_id": 81, "id": 96792}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667700.898917, "message": "That's the thing about Redis though, once you install it, you find all kinds of awesome ways to use it :) But I agree, doesn't seem absolutely necessary for this.", "group_id": 81, "id": 96793}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667457.5800769, "message": "Maybe you want a memcached session backend?", "group_id": 81, "id": 96770}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667467.6606081, "message": "say for each session I want to display a letter in the alphabet - a -> z, but I want to make sure each session can reserve a unique character for say 5mins, without any other session being assigned that letter", "group_id": 81, "id": 96771}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667539.5139821, "message": "@jsoncorwin So it seems like you're still going to want to use some sort of place to store the data of which session has which letter", "group_id": 81, "id": 96778}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667664.364413, "message": "@ericflo redis isn't already there, and I wouldn't install it just for this! I do like the thought though", "group_id": 81, "id": 96789}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667739.895076, "message": "your opinion matters...i'll put you in that category", "group_id": 81, "id": 96799}, {"user_id": 7, "stars": [], "topic_id": 5155, "date_created": 1297667495.768122, "message": "because there's no guarntee all requests hit the same process", "group_id": 81, "id": 96774}, {"user_id": 7, "stars": [], "topic_id": 5155, "date_created": 1297667498.9020219, "message": "n-teir and all", "group_id": 81, "id": 96775}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667509.5761721, "message": "does that alphabet example help any?", "group_id": 81, "id": 96777}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667561.134809, "message": "i was just wondering if there was some better way that was implemented than DB", "group_id": 81, "id": 96781}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667637.082206, "message": "@jsoncorwin Do you have Redis installed already though? It might not be worth the extra operational overhead", "group_id": 81, "id": 96787}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667762.7435031, "message": "lol", "group_id": 81, "id": 96801}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667584.0233951, "message": "nah, it won't be overly slow, i just wasn't sure it was worth dealing with storing in DB, if there was a better way", "group_id": 81, "id": 96783}, {"user_id": 41, "stars": [{"date_created": 1297667639.805423, "user_id": 1}], "topic_id": 5155, "date_created": 1297667636.0750999, "message": "i guess i could just use a simple table with a data column and an expiry column", "group_id": 81, "id": 96786}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667710.6131871, "message": "i'll settle for that, as the 'django lords' of this topic say it should work ok =p", "group_id": 81, "id": 96796}, {"user_id": 41, "stars": [], "topic_id": 5155, "date_created": 1297667725.800566, "message": "@ericflo - i'm always looking for a good excuse to tinker with new stuff....hopefully soon I'll get to install Redis!", "group_id": 81, "id": 96797}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297667726.0909939, "message": "Don't count me in that category", "group_id": 81, "id": 96798}, {"user_id": 7512, "stars": [], "topic_id": 5155, "date_created": 1297672963.192286, "message": "Maybe go with your caching backend. It's obvioulsy not reliably persistent - but might work for your example above.", "group_id": 81, "id": 97159}, {"user_id": 8740, "stars": [], "topic_id": 5155, "date_created": 1297678456.590292, "message": "I second @ericflo on that, Redis is amazingly versatile. We use it for both semi-temporary storage and as a message queue all over ep.io.", "group_id": 81, "id": 97614}, {"user_id": 4077, "stars": [], "topic_id": 5155, "date_created": 1297685666.5084071, "message": "Nobody else has mentioned it, and it isn't really the 'right' way to do this, but you could just do it with the filesystem, I suppose.  Create a file named 'a', and if it exists, don't issue it again.  Periodically, check the 'created_on' attribute of the file, and if it's older than 5 minutes, you could remove it.", "group_id": 81, "id": 98563}, {"user_id": 7, "stars": [], "topic_id": 5155, "date_created": 1297693516.4715919, "message": "@andrewgodwin ins'nt that an issue given you'd want different eviction strategies?", "group_id": 81, "id": 99966}, {"user_id": 8740, "stars": [], "topic_id": 5155, "date_created": 1297695387.3707891, "message": "@alex We eventually plan to run multiple instances of it, but at the moment, it's fast enough on a single box that isn't an issue.", "group_id": 81, "id": 100248}, {"user_id": 209, "stars": [], "topic_id": 5155, "date_created": 1297695722.2820361, "message": "Sounds like what you want is filesystem session storage, and then keep a cookie on the frontend of their session key", "group_id": 81, "id": 100324}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297720284.383966, "message": "@andrewgodwin That's exactly our experience too, we're using it for different purposes, but it's so fast that one instance is fast enough for us for now.", "group_id": 81, "id": 106138}, {"user_id": 8740, "stars": [], "topic_id": 5155, "date_created": 1297724470.8991771, "message": "@ericflo Given how good antirez is at this stuff, I half expect that when redis-cluster appears I'll be able to literally shove more hardware at it to make it scale.", "group_id": 81, "id": 107320}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297729006.3689189, "message": "Distributed systems are a whole different ballgame", "group_id": 81, "id": 108172}, {"user_id": 1, "stars": [], "topic_id": 5155, "date_created": 1297728994.782805, "message": "@andrewgodwin I'm not quite as sure about that as you are.", "group_id": 81, "id": 108170}, {"user_id": 7, "stars": [], "topic_id": 5155, "date_created": 1297733240.7775681, "message": "some aspects of redis are really not ammeanable to trivial clustering/distribution", "group_id": 81, "id": 108518}, {"user_id": 1736, "stars": [], "topic_id": 5155, "date_created": 1297733306.903136, "message": "The design antirez showed in the slides from the UK meetup seemed solid, but I can't say I'll be comfortable running it in production for a very long time. Even basic Postgres replication makes me nervous still.", "group_id": 81, "id": 108522}, {"user_id": 8740, "stars": [], "topic_id": 5155, "date_created": 1297763279.1666901, "message": "Well, I only said \"half expect\". Most of our stuff is built with eventual consistency in mind, so we can take a little worsening of the performance, but then again it's also built so it can be split into about 5 different redis servers. I suspect we may just throw more powerful hardware at the problem.", "group_id": 81, "id": 110040}]