GNUe Traffic #101 For 22�Dec�2003

By Arturas Kriukovas

"about half year ago, I was finding out about GNUe and then whote to this IRC, why do you use Python (I said "so exotic") .........now I see, you're completely right----so have fun, GNUE is super"

Table Of Contents

• Standard Format
• Text Format
• XML Source
• Introduction
• Threads Covered

  1.	15�Dec�2003		AppServer
  2.	15�Dec�2003		Moving to svn

Introduction

1. AppServer

15�Dec�2003�Archive Link: "[IRC] 15 Dec 2003"

People: Jeff Bailey,�Reinhard M�ller

Jeff Bailey (jbailey) noticed that if "appserver uses xml-rpc" , "is it possible to do some sort of authentication on that, or is it like corba, where you just pray the person has the rights to make the call?" Reinhard M�ller (Reinhard) corrected that statement "appserver uses xml-rpc" isn't a 100% correct. "Appserver uses whatever the gnue rpc library provides" . Jeff said using "xml-rpc/soap over an http transport violates do-one-thing-well architecture" .

2. Moving to svn

15�Dec�2003�Archive Link: "[IRC] 15 Dec 2003"

People: Jason Cater,�Daniel Baumann,�Jan Ischebeck,�James Thompson

It was agreed that there exist a consensus to move to svn http://subversion.tigris.org on ash.

However, Jason Cater (jcater) was not sure "about svn+ssh vs apache" . "the webdav support sounds really neat, but scares the heck out of me" addmitted he, because "apache auth methods" are used. Jason was also interested whether it would be "easy to go from svn+ssh to apache2 later on" . Daniel Baumann (chillywilly) expected it to be easy - "the repo is in the same format" . Jason offered starting "with svn+ssh, besides, if we went w/the other solution that's more to do, as apache2 isn't on ash" .

Later, Jan Ischebeck (siesel) asked what "repos structure should we use? Trunk/gnue-common trunk/gnue-forms branches/gnue-test-common... or gnue-common/trunk gnue-common/branches..." Jan "would prefer the first, as it would be easy then to check out the whole gnue tree and still be able to use the same setup-cvs.py which we use now. It would mean using just one svn repository, but we should be able to let it update different cvs repository as setup on savannah now. I think its easier to have the whole gnue project in one svn repository as it allows moving files from reports to common without loosing history but it is still possible to just check out gnue-common or gnue-forms etc." Jason grumbled about have moved "to gnue-* in cvs" . The was a reason to do so, but noone know remembered it. Jan agreed with Jason - "yeah, typing a "for .. " loop everytime to update gnue is bad" . "Nevertheless using one tree with svn shouldn't be a problem, as we can do finegrained security with svn and it is possible to check out the tree as a whole (trunk/gnue-*) or single subdirs /trunk/gnue-common /trunk/gnue-forms ... even checking out just /trunk/gnue-common/src/datasource/drivers/postgresql is possible" .

On 17 Dec, James Thompson (jamest) noticed that svn's hook system is "much easier than cvs's" .

�

�

�

�

�

�

Sharon And Joy
�