Hacker News new | past | comments | ask | show | jobs | submit login

Looks interesting, but there seems to be a built in conflict where you say it's meant for "long running", but then also reap these after 24 hours.

Can you clarify how they are reaped? Is it a straight timer, or only after X hours of no reads + no writes?




Oh, I should update the text to clarify: sessions are garbage collected 24 hours after the program has terminated (so after there's no possibility of the program producing more output).

There will probably be more options for persistence once there's an accounts system (to prevent abuse).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: