Stories
Slash Boxes
Comments

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

acs (1437)

acs
  (email not shown publicly)
http://barrapunto.com

Barrapunto slashcode developer.

Journal of acs (1437)

Tuesday October 23, 01

Patches for Fry

12:45 AM
Slash

The new Fry version will have some patches that enables the use of multivalue HTML params in slashcode. Great to throw away this patches from the Barrapunto CVS.

Sunday September 23, 01

Barrapunto now 2.0

05:59 AM
Bugs

After some months in migrating the new features we use in
Barrapunto (ACLs, indexes to group the stories in several sections, ecolutions to enable the re-edition of stories
as a new story, MySlash in order our users can manage its own section and some othe features) as slashcode plugins with some minor modifications in the libraries, we have
Barrapunto.com now running using slash 2.0.

Some of our editor has started to play with the templates
and change it for some sections in order to take another L&F in each section.

At the begining we are worried about the load of the machine with this new software, but after the cache was activated and the AC access to index.shtml, everything seems to work well for our dual PIII 750 Mhz 1 GB RAM machine. I think we can serve 100.000 pages/day with this machine before we have to use to machines, one for the database and the the other for the web server.

Monday August 27, 01

First story in slashcode

09:38 AM
Bugs

Today I have put my first story in slashcode. Great!
I try to do a great job here in slashcode and learn everything I can ;-)

Friday June 08, 01

Plugins in slashcode

01:58 AM
Bugs

I think that it will be wonderfull to has all the plugins accesible from:

http://slashcode.com/plugins.pl

It seems to me that this place is the correct place to
share our work. I will try to discuss it with the slashcode
webmaster, Krow I think.

Thursday June 07, 01

An Event System

11:52 AM
Bugs

Many people ask us in Barrapunto.com that they want to receive and e-mail when somebody reply a comment. Ok, let's try to do it bue, why only control when somebody reply a comment? Maybe, we can catch also when a new story enter the system or when a new poll is put.

But we dont' want to modify the slashcode so, how can we implement this? Simple, we have two tables:

  • event
  • event_subscription

A daemon called "eventd" takes the events from the slash database and put the in the event table. Then, it process the events and using the event_subscription table, builds and email for the users informing with the new events. And then, it deletes all the events. This process is repeted.

The hard thing in the system is the scalability. We are now thinking about it, but to take in memory the event table and the event_subscription table in hash tables could be the solution, no?

If you want to see it, take a look at our CVS.