--- Log opened Wed Aug 05 00:00:55 2009
03:08 < Gilly> Hello! I'd like to know how MACID works regarding memory/disk. Does it keep stuff in the memory even if it's not being asked for?
07:05 < mightybyte> Gilly: Yes, everything is kept in RAM, but a transaction log is written to disk so the state is always recoverable in the event of a program crash.
07:06 < Gilly> Alright - doesn't look like that's the way to go for my blogging software then... I'm quite low on RAM.
07:07 < Gilly> Another question: What's the status of happstack-auth?
07:41 < mightybyte> Gilly: In what sense?  It uses happstack-state to store the user and session database.  I'm also using it in a production website.
07:58 < Gilly> Well - I meant to ask whether it's ready to use. I guess it is then :)
08:06 < mightybyte> Gilly: There are a few issues that need to be fixed in the long term, but on the whole it's useable.
08:06 < Gilly> Alright, thanks :)
08:06 < mightybyte> And I'll gladly accept patches :)
08:06 < mightybyte> One issue that comes to mind is that it doesn't clean up stale sessions.
08:07 < mightybyte> They will just accumulate in state over time, which is obviously not the best behavior.
08:07 < mightybyte> But I'm running on a fairly small amount of memory as well, and this doesn't make a significant difference with my current level of traffic.
08:09 < mightybyte> And if the only people logging into your bloggin software are the content creators, then happstack-auth should be fine since the content creators will probably be the only ones logging in.
08:09 < Gilly> clean up stale sessions means that when the user logouts the session is orphaned in the memory?
08:09 < mightybyte> Ugh, that sentence was horrible...I guess I'm still waking up. :)
08:10 < mightybyte> Yes
08:10 < mightybyte> No
08:10 < mightybyte> When the user logs out, the session is cleared.
08:10 < mightybyte> But if the user doesn't log out, and clears his cookies, then the orphaned session will remain in memory.
08:10 < Gilly> Ahh. What if someone opens a new session with the same username and password?
08:10 < Gilly> Is the old one wiped out then?
08:10 < mightybyte> No
08:11 < mightybyte> Because users can have multiple sessions (in the current architecture)
08:11 < Gilly> Alright. But yea - anyways - my situation won't take big hit from this... I'll probably have only a few guys blogging. (heh, maybe just me)
08:12 < mightybyte> And the library does have functions to clear the sessions.  So you could set up a way to do that manually.
08:12 < mightybyte> It will kill all active sessions, and users will have to log back in, but that's acceptable in some cases.
08:13 < Gilly> Yea.
08:13 < Gilly> Of course we could add a time variable to sessions and update that everytime the user loads a page.
08:13 < Gilly> And then wipe out old sessions occasionally.
08:58 < mightybyte> Yes, I haven't decided whether I want to do that or just restrict users to a single session.
15:08 < sm> g'day all
15:08 < sm> how do you write html entities like &nbsp; in a hsp fn ?
17:44 < gav> whats up happsters
20:29 < mae> hallo
--- Log closed Thu Aug 06 00:00:56 2009