[03:52:35] ** gpciceri has joined us [05:48:02] ** gpciceri has left IRC ("Leaving") [06:56:42] ** vlado has joined us [08:30:24] Current conditions at Winnipeg Int. Airportman., Canada: It is -40 C (-40 F), humidity is 65%, windspeed is 11.27 km/h, and visibility is 3.22 km. (Information current as of 2004.01.30 1200 UTC). [08:44:17] -40C [08:44:59] :) [10:35:31] ** vlado has left IRC ("ChatZilla 0.9.52B [Mozilla rv:1.6/20040113]") [10:35:42] ** gpciceri has joined us [10:36:06] big thread, the peak-webware integration one [11:22:16] ** gpciceri has left IRC (Remote closed the connection) [12:30:33] ** gpciceri has joined us [13:19:45] * _jpl_ knows that -40C is -40F. :) [13:24:48] <_jpl_> Yes, good to see more discussion about PEAK and web app development. [13:25:18] <_jpl_> I also need to put a web front end on a PEAK app, and have been thinking about the various options. [13:25:56] I have the proble to figure vhow to reuse peak components in a web scenario [13:26:11] I mean, [13:26:23] I build some models, storages and so on [13:26:43] then it's clear how to build a CLI application [13:27:06] but I still wonder how to reuse the components under a web framework [13:27:45] or to be able to use a web framework as additional components [13:41:08] <_jpl_> It shouldn't be difficult to simply use PEAK components within a framework like WebWare, for example. You can replicate the various things done by /usr/bin/peak within other frameworks, things like setting up a configuration root, reading config files, etc. [14:23:56] never mind. i don't know how to do the canonical peak.web app [14:24:27] _jpl_, well most 'merican's dont' :) [14:32:37] <_jpl_> We're not all as stupid as our leaders. :) [15:00:55] fair enough [15:28:28] <_jpl_> watch out for frostbite [16:26:34] ** _jpl_ has left IRC ("Leaving") [16:33:19] if you dress correctly that's not an issue [17:43:56] rowr [17:46:22] ** gpciceri has left IRC ("Leaving")