[Serdev] SER architectural decisions - was: So who/what is SER for, anyway?

[Andrei Pelinescu-Onciul]

On Jan 25, 2007 at 09:35, Greger V. Teigre <greger at teigre.com> wrote:
> Greger's comment: The next discussion item I identified in Dragos' post 
> was the topic of architectural decisions and who make them and when. I 
> call the thread "SER architectural decisions"
> ----------------------------------------------
> 
> To me, the whole thing looks like a pile of hacks. When was the last
> time that there was a overall design discussion? I think that modules
> and extensions just grew around, but nobody wanted or had the power to
> cut some dead branches, enforce some policies and specify some clear
> internal interfaces. If one person would take care of it end-to-end, OK,
> but it's not the case.

modules were there almost from the beginning. It's true however that ser
outgrew the current module interface and it needs a change.
Unfortunately we cannot make this change overnight and that's why we
have to live with numerous hacks.

Other example of things related to the module interface that need to
be changed/improved/added:
- avps (ineficient, memory consuming, module inter comunication hack
  that far outgrew its original limited purpose)
- script engine (variable number of parameter support, better avp/vars
  support a.s.o)
- config params (unified interface for all the configurable parameters
  cmd line or config)
-  simplified cfg.lex, cfg.y

All this stuff will take a lot of time, but it will eventually happen.

Andrei