02-17-102 13:03:16 This meeting of WarpDoctor is now in session. 02-17-102 13:03:49 2. Sector, you taking the log? 02-17-102 13:04:14 3. Old Business 02-17-102 13:04:25 But of course 02-17-102 13:04:40 a. We need to settle to the time of the meeting. 02-17-102 13:05:20 I move that we keep the current time (4:00p) as a permanent change. 02-17-102 13:05:31 Works for me 02-17-102 13:05:34 second 02-17-102 13:05:36 Sundays, of course. 02-17-102 13:05:47 Discussion? 02-17-102 13:05:49 agree 02-17-102 13:06:00 Agree to Discuss? 02-17-102 13:06:20 no.. i agree to 4:00pm EST 02-17-102 13:10:02 All in favour, type Aye. 02-17-102 13:10:06 aye 02-17-102 13:10:06 aye 02-17-102 13:10:11 aye 02-17-102 13:10:14 aye 02-17-102 13:10:15 Affirmative 02-17-102 13:10:17 Aye 02-17-102 13:10:36 Opposed? 02-17-102 13:10:48 Carried. 02-17-102 13:11:22 aye 02-17-102 13:11:51 Mark... opposes? 02-17-102 13:12:23 I was just late in Ayeing 02-17-102 13:12:38 Though actually an hour earlier would be better for me 02-17-102 13:13:26 I'm flexible. Anyone else feel that way? i.e. 3:00p 02-17-102 13:13:37 3:00pm is fine with me 02-17-102 13:13:56 Oh God I didn't mean to start a whole new issue 02-17-102 13:13:57 I am flexible as well.. I don't care what time we have the meeting 02-17-102 13:14:16 4PM is fine 02-17-102 13:14:52 so.. I'll say aye to just about anything :) 02-17-102 13:14:53 Well, I've notice people start leaving around 5:30 or so. That's why I'm pursuing it, actually. 02-17-102 13:15:09 3:00 is fine with me too 02-17-102 13:15:46 Walter, you're right. 5:30 is a bit late to go. 02-17-102 13:15:50 IMHO 3.00 is better for Europeans too ;-) 02-17-102 13:16:20 OK, the chair is open to a new motion. :-) 02-17-102 13:16:41 Move we change meeting time to 3:00 PM 02-17-102 13:16:47 second 02-17-102 13:17:14 Discussion? 02-17-102 13:19:13 I think we pretty much had our discussion, before we called for the motion. 02-17-102 13:19:45 All in favour of changing the time of the meeting to 3:00p on Sundays, type Aye. 02-17-102 13:19:52 aye 02-17-102 13:19:57 aye 02-17-102 13:20:00 Ok 02-17-102 13:20:01 Aye 02-17-102 13:20:02 aye 02-17-102 13:20:05 aye 02-17-102 13:21:08 All opposed. 02-17-102 13:21:26 Carried. 02-17-102 13:26:00 OK, let's move on. 02-17-102 13:26:08 4. Status Reports. 02-17-102 13:26:29 1. Jeremy--Web site? 02-17-102 13:26:58 Rat-Salad, is there anything to report this week? 02-17-102 13:27:12 website is in the process 02-17-102 13:27:39 I just haven't had much time to work on it this week 02-17-102 13:28:08 but when the update is ready it'll be much improved in ways 02-17-102 13:28:53 I think we discussed this last week.. so lets not get into that though 02-17-102 13:30:31 Let's continue with the status reports. 02-17-102 13:30:56 ii. Lalcan--Compatibility Page 02-17-102 13:31:45 Jeremy told us earlier that Lalcan is tied up with work, so is limited in what he can do here for now. 02-17-102 13:32:24 I guess for now, we'll just let the page sit and wait for him to work on as he gets time. 02-17-102 13:34:06 yeah 02-17-102 13:34:48 iii. Ceilidh - Currently working with 3 forums, but I haven't done any more work on it this week. 02-17-102 13:35:40 Later on, I want to refine the password system and add a 4th forum. 02-17-102 13:37:27 I also want to interface it with our email server, but that's going to have to wait for the virus problem to get solved, and then I have to work with Ceilidh support and probably Wilson Rook as well. 02-17-102 13:37:47 Any Discussion? 02-17-102 13:38:08 On Ceilidh, I mean. 02-17-102 13:39:27 iv. Yes, Doug. Now it's your time to tell us what you've been up to. :-) 02-17-102 13:40:32 I am running behind on my first (major) task 02-17-102 13:40:42 I was planning on the meeting at 6:00. I see is now back to 4:00 02-17-102 13:40:59 How many have read Doug's WarpDoctor email? 02-17-102 13:41:02 Wrong again - it's now at 3 02-17-102 13:43:54 So I figure we are/will be about 2-3 weeks late 02-17-102 13:49:05 Doug, could you give us a brief summary of the email you sent to WD@os2voice.org? 02-17-102 13:50:14 Connection manager should speed up each database access from CGI programs 02-17-102 13:50:22 It consists of three components 02-17-102 13:50:36 One fo the components I already had built but needed to modify 02-17-102 13:50:38 Down side is the crashed drive was only 1 month old and the current drive is same make and similar model. 02-17-102 13:50:54 The other two are new from scratch 02-17-102 13:51:21 I have run into considerable problems in areas that I didn't think would be problems 02-17-102 13:51:35 Latest is that I have been bushwacked by BLOBS 02-17-102 13:52:03 How are you implementing them? 02-17-102 13:52:11 The ODBC and IBM DB2 CLI document is wrong when describing how BLOBs are sized and it took a while to figure that out 02-17-102 13:52:14 Just curious. :-) 02-17-102 13:52:50 That's my allt-time favourite...incorrect documentation!! 02-17-102 13:53:18 For WD I hope that one CLOB (character Large Object) of 64k will be large enough to hold all the text associated with a single item/page 02-17-102 13:53:37 The other fields for a row will hold categories, OS, etc. 02-17-102 13:54:04 Doug, I don't want to get you off on a tangent, but 02-17-102 13:54:22 theres one really big page on the site now... I bet it alone is more than 64k hehehe 02-17-102 13:54:43 Is that the one on PC systems? 02-17-102 13:55:07 will one CLOB hold, say a large REXX program? I understand they can be as large as 64K. Can they be bigger? 02-17-102 13:55:09 the netscape documentation 02-17-102 13:56:03 Walter - Rat - maybe I'll will have to increase the size. 02-17-102 13:56:33 To be save, it would be a good idea, but maybe save it for Phase 2. 02-17-102 13:57:02 Rexx programs can be larger than 64K, but it is better if they are 64k or smaller because then the encoded-bytes are stored in the extended attributes so the interperter doesn't have to re-encode them 02-17-102 13:57:31 I recommend two things. 1. increase the size to 128K 2. Larger projects/pages could referance an external file that can be downloaded via ftp or http 02-17-102 13:58:47 Increasing the size won't affect much in the way of programming. It will just mean that the CLOB will be transferred twice since the max pipe buffer size is 64k 02-17-102 13:58:55 Bren, I live in Kitchener, Ontario. :-) 02-17-102 13:59:00 twice = 2 pieces 02-17-102 13:59:57 http://www.warpdoctor.org/lib/info/jsprefs.html hehe check it out 02-17-102 14:01:22 Generally though I think that most pages can (and should) be broken into smaller chunks 02-17-102 14:01:34 With references to other parts if necessary. 02-17-102 14:01:57 ohh, I agree that it needs broken up.. but doing so is a task 02-17-102 14:02:06 That makes the page server quicker and most people don't want to wade through hugh pages to get to the info they want. 02-17-102 14:02:15 Doug, are you _sure_ leaving REALLY big files to PHASE 2 wouldn't speed up getting Phase I running? 02-17-102 14:02:53 No - the data access process is purely generic - meaning that it detects the size of the data in the CLOB/BLOB and handles it accordingly 02-17-102 14:03:36 That actually was the problem with the documentation - because I was not able (until last night) to see the size of the actual data in the BLOB rather than the max size declared for the BLOB field 02-17-102 14:06:50 The only other thing on the schedule that worries me is the task(s) related to building a screen for changing existing items 02-17-102 14:08:13 I already have something that works but the undo-redo hasn't been implemented yet 02-17-102 14:08:48 so I don't know how long that will take. Maybe just release without undo-redo and implement later. 02-17-102 14:10:08 end.... 02-17-102 14:12:48 OK, thanks. I think you should release it without the UN/RE-DO and implement that later, as you suggested. 02-17-102 14:13:23 Ok - will do 02-17-102 14:13:28 I agree 02-17-102 14:16:14 I hope to get together with Gord this week (if he recovers from hard drive death) to start getting the data entered into the database 02-17-102 14:17:42 Is there any discussion on Doug's report? 02-17-102 14:18:51 OK, let's move on. 02-17-102 14:19:00 5. New Business 02-17-102 14:19:27 Does anyone have any business they wish to add to the agenda? 02-17-102 14:19:38 Now's the time! :-) 02-17-102 14:21:05 6. Impact on our schedule. 02-17-102 14:21:23 We pretty much covered that under Doug's report. 02-17-102 14:22:11 Doug, Rat-Salad, can you think of anything else that might cause our schedule to be revised? 02-17-102 14:25:47 OK, let's move on. 02-17-102 14:25:58 7. Open Discussion. 02-17-102 14:26:47 Is there any generaly discussion relevant to WarpDoctor? 02-17-102 14:26:57 general 02-17-102 14:28:39 Move to adjurn. 02-17-102 14:28:46 second 02-17-102 14:28:59 All in favour, type Aye. 02-17-102 14:29:02 aye 02-17-102 14:29:07 Aye 02-17-102 14:29:28 Aye 02-17-102 14:29:46 Aye 02-17-102 14:30:07 All opposed? 02-17-102 14:30:38 Carried.