| 00:14.39 | *** part/#storm mikex2 (n=mikael@193.11.146.205) |
| 00:29.02 | *** join/#storm danilo__ (n=danilo@static-213-198-236-193.adsl.eunet.rs) |
| 00:59.33 | *** join/#storm mikex2 (n=mikael@193.11.22.34) |
| 02:57.39 | *** join/#storm danilo_ (n=danilo@static-213-198-236-193.adsl.eunet.rs) |
| 09:28.40 | *** join/#storm oubiwann_ (n=oubiwann@c-24-8-208-199.hsd1.co.comcast.net) |
| 10:01.08 | *** join/#storm jukart (n=jukart@d86-32-163-51.cust.tele2.at) |
| 11:07.52 | *** join/#storm mikex2 (n=mikael@193.11.22.34) |
| 11:40.12 | *** join/#storm yosafbridge (n=yosafbri@li14-39.members.linode.com) |
| 12:35.14 | *** join/#storm gabriel_ (n=gabriel@d24-141-18-191.home.cgocable.net) |
| 12:46.11 | gabriel_ | is it possible to use storm's cache to store the result of calculations performed on storm-managed data? The key is that I'd like to have the results automatically invalidated when storm decides the underlying data is no longer valid |
| 12:46.30 | gabriel_ | or is this the type of thing that hooks should be used for? |
| 13:06.30 | therve | gabriel_: right, you should cache things in the objects themselves |
| 13:06.42 | therve | and use __storm_invalidated__ to clean the cache |
| 13:11.32 | *** join/#storm jukart (n=jukart@d86-32-163-51.cust.tele2.at) |
| 13:48.41 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 13:59.19 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 14:14.01 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 14:16.33 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 14:20.39 | *** join/#storm zmijunkie (n=chatzill@i53870518.versanet.de) |
| 15:46.08 | *** join/#storm mikex2 (n=mikael@193.11.146.205) |
| 15:46.45 | *** join/#storm bigdog (n=scmikes@72-197-8-8-arpa.cust.cinci.current.net) |
| 15:55.39 | *** join/#storm jukart (n=jukart@d86-32-163-51.cust.tele2.at) |
| 16:38.26 | gabriel_ | therve: ok, that makes sense. thanks. |
| 16:41.57 | gabriel_ | is there documentation somewhere that lists/explains all the hooks available? The tutorial only has storm_loaded, and I don't see anything on the manual page |
| 16:45.07 | *** join/#storm webmaven_ (n=webmaven@c-68-35-25-63.hsd1.nm.comcast.net) |
| 17:32.58 | therve | gabriel_: not that I know :/ |
| 17:41.21 | gabriel_ | grepping through storm's source for "__storm_" turned up __storm_invalidated__, __storm_object_info__, __storm_class_info__, __storm_table__, __storm_primary__, __storm_order__, __storm_invalidated__, __storm_pre_flush__, __storm_flushed__, __storm_loaded__ |
| 17:41.50 | gabriel_ | therve: of course, some of those are obviously not hooks |
| 17:42.07 | gabriel_ | is that list missing any? |
| 17:44.15 | gabriel_ | i guess grepping for "_run_hook" would make more sense... |
| 18:10.57 | *** join/#storm jukart (n=jukart@d86-32-163-51.cust.tele2.at) |
| 19:55.27 | *** join/#storm mikex2 (n=mikael@193.11.146.205) |
| 20:09.20 | *** join/#storm rockstar` (n=rockstar@starscream.eventuallyanyway.com) |
| 22:17.50 | *** join/#storm danilo_ (n=danilo@static-213-198-236-193.adsl.eunet.rs) |
| 22:23.08 | *** join/#storm jkakar (n=jkakar@S0106001ee57a879c.vc.shawcable.net) |
| 22:24.34 | jkakar | gabriel_: Thanks for adding notes to the manual about the hooks Storm provides. Seeing that wiki diff show up in my email made me smile. :) |
| 22:28.04 | gabriel_ | jkakar: no problem! I'll try to keep adding information to the docs as I pick it from your brains over IRC :) |
| 22:29.04 | jkakar | gabriel_: Thanks, that's much appreciated. Our documentation story needs a lot of love, as you know. :) |
| 23:24.47 | *** join/#storm mikex2 (n=mikael@193.11.22.216) |
| 23:25.12 | *** part/#storm mikex2 (n=mikael@193.11.22.216) |