| 00:10.43 | *** join/#storm webmaven (~webmaven@c-68-35-25-63.hsd1.nm.comcast.net) |
| 00:13.01 | *** join/#storm webmaven (~webmaven@c-68-35-25-63.hsd1.nm.comcast.net) |
| 00:13.15 | *** join/#storm webmaven_ (~webmaven@c-68-35-25-63.hsd1.nm.comcast.net) |
| 00:24.45 | *** join/#storm deam (deam@is.really.feared.eu) |
| 01:52.28 | *** join/#storm keppla (~keppla@i577B30ED.versanet.de) |
| 02:38.21 | *** join/#storm jdobrien (~john@24.18.88.184.cfl.res.rr.com) |
| 05:43.35 | *** join/#storm jamesh (~james@canonical/launchpad/jamesh) |
| 05:48.54 | *** join/#storm bcward (~bcward@134.82.201.153) |
| 05:51.09 | bcward | I have an application which can run for several days between queries, and I just discovered (the hard way) that the connection can be lost over such long periods of time. Is there a recommended way to handle this? Or should I just create a new connection for every query if they occur so infrequently? |
| 07:49.27 | *** join/#storm zmijunkie (~chatzilla@i538713E1.versanet.de) |
| 08:01.55 | *** join/#storm elmom_ (~elmom@hoasnet-fe29dd00-137.dhcp.inet.fi) |
| 12:47.39 | *** join/#storm danilos (~danilo@canonical/launchpad/danilos) |
| 14:23.50 | *** join/#storm shaunm (~shaunm@WS-ESR1-74-215-234-197.fuse.net) |
| 14:54.02 | *** join/#storm stub (~stub@88.208.89.139) |
| 16:19.49 | *** join/#storm niemeyer (~niemeyer@201-11-213-235.pltce701.dsl.brasiltelecom.net.br) |
| 17:07.16 | *** join/#storm shaunm (~shaunm@WS-ESR1-74-215-234-197.fuse.net) |
| 20:01.33 | *** join/#storm shaunm (~shaunm@WS-ESR1-74-215-234-197.fuse.net) |
| 20:04.09 | *** join/#storm keppla (~keppla@87.123.15.0) |
| 21:17.32 | *** join/#storm fcorrea (~fcorrea@201-62-110-55-ma.static.vivax.com.br) |