[Users] Re: [Devel] roadmap to v1.1.0

[Daniel-Constantin Mierla]

Hi,

the new roadmap is now online.
http://openser.org/roadmap.php

I collected all the suggestions sent on the mailing list, please let me 
know if something was missed. The roadmap is just a guide for the new 
release, many other features will be implemented till the next release, 
although some of the one listed in the document may not be ready in this 
time frame.

Please use the tracker on sourceforge to request new features, it is 
easier to review and manage them.
http://sourceforge.net/tracker/?group_id=139143

The document from the web site will be updated accordingly from time to 
time.

Cheers,
Daniel


 

On 11/03/05 18:47, Daniel-Constantin Mierla wrote:
> Hi everybody,
>
> we are trying to collect the items to be included in the roadmap to 
> the next release. I have written a draft with the ideas discussed on 
> the mailing list, the items which were not accomplished in v1.0.0 and 
> a few more. There is no weight attached, and the presence in the 
> roadmap does not imply that the feature will be for sure implemented 
> until the next release. The roadmap should guide the development of 
> the project.
>
> Please send your suggestions, if possible with some description. As a 
> general rule, the features to be implemented must follow the standard, 
> if they are related directly to SIP, or they must have a clear and 
> common usage in real cases.
>
> Cheers,
> Daniel
>
> ------------------------------------------------------------------------
>
> Draft of the roadmap to OpenSERv1.1.0
> -------------------------------------
>
> OpenSER core:
>
> - generic communication interface which must offer an abstract layer between
>   core/modules and transports (e.g., fifo, unix sockets)
> - move the code of the implemented trasports as module
> - NAPTR lookup
> - TLS multi-domain support
> - TLS configuration values to be set via a module, to keep core less exposed
>   to often changes
> - better error reporting and handling
> - pseudo-variables to be introduced in different modules
> - security checks of destination addess (white/black lists)
> - memory defragmentation
> - tcp enhancements
> - OpenSER command line interface (terminal)
>
> OpenSER modules:
>
> [acc]
> - possibility to disable values from db_fmt
>
> [avpops]
> - more coherent format of the parameters (=>to be used the one
>   from pseudo-variables)
> - ability to take the name of the AVP to be loaded from the value
>   of another AVP
> - global avps - avps to be stored during run time, shared between processes
> - local avps - avps to be stored locally, specific per script, not per
>   transaction
>
> [cpl-c]
> - possibility to configure table and columns' names
> - import registrar paramters insted of redefine
>
> [dbtext]
> - replace support
> - reload support
>
> [dispatcher]
> - serial forking when selected destination fails
> - database support
>
> [enum]
> [-] - parallel/serial forking based on order and preference fields
>
> [postgres]
> - connection pool
> - shift to memory manager used by openser
>
> [tm]
> - unification of t_relay_to_*() in a form of t_relay_to("proto:host:port")
>
> [uac]
> - qop authentication support
> - proper CSeq value after authentication challenge
>
> [usrloc]
> - better handling of the natted contacts, to uniquely identify a contact
> - cacheless usrloc
> - path support for registrations
> - sip instance support
> - possibility to attach to a contact a set of values (similar to log_extra
>   in acc)
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>