eiffelroom - drupal - Comments

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!)

Drupal vs. Xoops

neallester — Mon, 02 Apr 2007 11:32:34 -0700

I find myself advising someone on the selection of a CMS for a web site. Xoops and Drupal seem like the top contenders for them. You gave Drupal a recommendation by using it; I was just wondering why.

The most important reason

juliant — Mon, 02 Apr 2007 10:20:00 -0700

The most important reason was probably that I didn't now Xoops ;)

But after a quick look at it I still think Drupal was the right choice:

Input format customization for Xoops seems not as powerful as the Drupal alternative. Mediawiki format and syntax highlighting make it easy for us to use this site since we are all used to it from the EiffelStudio wiki already as it works exactly the same here.
Clean URLs: This is especially important for search engines. Drupal supports it out of the box, but Xoops on the other hand has not even clean URLs on their homepage.
Plugin mechanism: Drupal's plugin mechanism is simple yet powerful as any module can alter behaviour of core modules and even other modules. The Xoops way (without looking at it really close) looks like the modules are more isolated and don't interact too much.

But as I said, I don't know the inner workings of Xoops and after working with Drupal my opinion may be biased ;)

(Do you know more about Xoops? Why do you propose it?)

Choosing Drupal

neallester — Sat, 31 Mar 2007 10:05:43 -0700

Why did you choose Drupal over Xoops?