eiffelroom - goanna - Comments

I know that Berend likes

bayt — Wed, 07 Nov 2007 01:42:55 -0800

I know that Berend likes Perforce, but as for CVS, there are good migration tools to SVN and client support for SVN is quite a convincing argument nowadays. And to give Origo a try it should be OK.

I must have missed your question - we have written the issue tracker ourselves. As always on Origo we're also evaluating external solutions like Mantis, Bugzilla and also Jira, but for now we use our own solution.

Berend uses Perforce

colin-adams — Tue, 06 Nov 2007 23:28:54 -0800

I think he would be more convinced if you were using Perforce rather than Subversion.

BTW, I still haven't seen an answer to my question as to what software is used on Origo for issue tracking.

Colin Adams

Yes Patrick, I wrote to

bayt — Tue, 06 Nov 2007 12:29:24 -0800

Yes Patrick, I wrote to Berend explaining how much of Origo is written in Eiffel - lets hope that convinces him! :)

It's not that hard to

patrickr — Tue, 06 Nov 2007 08:29:25 -0800

It's not that hard to integrate it with Apache, but I prefer using lighttpd for fastcgi, as it has much less overhead, performs faster and scales better. As an added bonus it also provides loadbalancing features already builtin.

It's great that Goanna is now on Origo, so I can watch changes to it easily. It would be great if eposix would switch to Origo as well.

I agree, I really like the

mtn — Mon, 05 Nov 2007 09:52:29 -0800

I agree, I really like the way origo does things: Emphasis on ease of use and still powerful. Every few weeks I find a cool new feature :-) keep up the good work!

About goanna: I never used it so far, is it difficult to integrate goanna with Apache 2? Or what is the preferred way to run your application?

-- mTn-_-|

Will update tutorial

bayt — Sun, 04 Nov 2007 09:26:40 -0800

Thanks Neal,

I will integrate this info in the tutorial on Goanna's Origo page too.

Great Tutorial

neallester — Sun, 04 Nov 2007 09:19:52 -0800

Thank you for doing this, Till. One thing I'd like to add is that the parameter collections are for validating the semantics of a submitted form, not for validating user input.

Mandatory Parameter Collection - These are mandatory at the form processing level, not required fields in the form the user sees. Typically, these are a html hidden elements used to verify that some system state is the same at form processing time as it was at form generation time. For example, it might contain the user name of a logged in user to prevent them from submitting a form, logging out, logging in as a new user, and then using the back button to resubmit the previously generated form for the previous user.

Required Parameter Collection - These are html elements which must be present in the form for correct processing to occur or whose absence indicates a serious bug in the form generation routine or an attack on the web site. This doesn't necessarily mean that the user must provide a value for the element. "address_line_2" on a registration page might be an example of a required parameter for which no user input would be required.

Optional Parameter Collection - These are elements whose absence from a submitted form is expected sometimes. No processing for this parameter will occur if they are not present in the form.

Add If Absent Parameter Collection - These are elements whose absence from a form has meaning. html checkbox elements provide a typical example. If they are not present in the form submittal, a PARAMETER_PROCESSING_RESULT for them is added so that the appropriate processing for their unchecked state will occur.

Validating User Input

Each GOA_REQUEST_PARAMETER is responsible for validating the input it receives from the user. Since receiving invalid input is expected, this does not interrupt request processing. Typically, invalid user input produces

"not PARAMETER_PROCESSING_RESULT.is_value_valid"

which in turn triggers the redisplay of the form with an error message. Several GOA_REQUEST_PARAMETER descendents implement this behavior for common data types.

Project Automation Book

jvelilla — Tue, 17 Jul 2007 09:54:00 -0700

This book ( http://www.pragmaticprogrammer.com/sk/auto/ ) talk about this topic and show good examples.

You can see Buildix ( http://buildix.thoughtworks.com/ ) an Agile development platform with

1) Subversion for Source Control

2) Trac for a Wiki, Bug-Tracker and general Project Management

3) Cruise Control for Continuous Integration

I basically just followed

patrickr — Mon, 16 Jul 2007 07:44:20 -0700

I basically just followed the getting started page from cruisecontrol

http://cruisecontrol.sourceforge.net/gettingstartedsourcedist.html

Instead of ant files I simply used bash scripts, our configuration can be found under

https://svn.origo.ethz.ch/origo/core/trunk/examples/cruisecontrol/config.xml

More details

manus_eiffel — Sun, 15 Jul 2007 16:21:03 -0700

Do you have a page that goes more in the details of how one would setup such an environment?

Thanks, Manu

This setup is a great advantage

bayt — Fri, 13 Jul 2007 04:54:29 -0700

I'd just like to add here that this setup proves to be extremely useful in the development of Origo. We detect regressions almost instantly and getting an email after a successful build and test of Origo is always cool. The system even let's us know how long it took to do a clean build - at the moment a bit more than twenty minutes.

A similar approach should in my opinion be used for every bigger project.

Goanna and webserver

patrickr — Fri, 20 Apr 2007 02:16:10 -0700

Goanna is used for the xmlrpc interface using fastcgi and apache. The website itself is based on Drupal and uses php. I also did some testing with lighttpd which also seems to work fine with goanna fastcgi and which is a lot faster and scales better http://origo.ethz.ch/index.php/Performance

First thoughts

colin-adams — Fri, 20 Apr 2007 00:36:22 -0700

Very interesting. Are you using Goanna as part of the software? There is no tag for it. What are you using to provide HTTPS communications?

Colin Adams

External access will be available soon

patrickr — Thu, 19 Apr 2007 14:57:01 -0700

There will be access to the API very soon. The API is split in an internal and external part, the internal part is very small and almost everything is also available externally. For external applications, login will be done with a per user key to prevent brute force password hacking attempts.

http://origo.ethz.ch/index.php/API

Another student is already working on creating plugins for EiffelStudio, VisualStudio and Eclipse

Client tools

paulbates — Thu, 19 Apr 2007 09:51:55 -0700

I've already got my project page up!

I forgot to ask till, and maybe you know. is the XMLRPC accessible to external clients? Just thinking about the client tools domain. Actually it would nice to have a Eiffel framework API we could use for the purpose of developing tools (We developers only want more, more, more!)