SourceForge.net Logo

news

BERSERK V1.0 Release candidate 3 has been released March the 12th, 2004. (see notes)

BERSERK V1.0 Release candidate 2 has been released November the 28th, 2003. (see notes)

BERSERK V1.0 Release candidate 1 has been released November the 10th, 2003. (see notes)

status

On March's, 2004 last week a paper on BERSERK was presented at Iadis Applied Computing 2004. More information on the paper on Publications section.

BERSERK is currently at V1.0 release candidate 3. From RC1 to RC2 few things changed including some bug fixes, and a few new features. Details on these changes can be found on RC2 release notes.

The first version of this software is the result of a code refactoring done in the core of Fenix Project in the scope of a Course I did in my graduation at IST.

At the time of BERSERK's first release there was only developer (Gonçalo Luiz). Now some developers from the Fénix Project (see this page) has been added and they are contributing.

We are currently planning the new features for BERSERK V2.0. Some things you may expect include Parameterized Filters and run-time filter, chain and service creation. Stay aware :)

future work

Some of the features BERSERK should provide in the future as well as short description and the proposed implementation.

  • Port BERSERK to C# programming language
    • since BERSERK is open-source (LGPL) forward engineering is possible.
  • Parameterized Filters
    • by the release of BERSERK V1.0 filters only have access to service’s parameters. That is, there is no way to explicitly pass filters its own parameters
    • add expression power to filter composing language, enabling first order predicates
  • Service Groups
    • allow the creation of grouped services. This allows the macro-management of services groups; for example delegate entire services groups access on users
    • create service type concept and service/ service type associations
  • GUI Administration Tool
    • allow a user-friendly administration tool instead of directly edit the XML files and / or database tables create write methods to BERSERK’s storage objects (filter, service and filter chains definitions).
    • Create web-based interface
  • Distributed Runtime
    • provide remote invocation capabilities
    • use Java RMI, C# remoting or soap web-services