HI Raymond,
I think was already mentioned in usrloc section as "cacheless usrloc" -
integrating this into usrloc will be a more elegant way to do it than
having another module.
regards,
bogdan
Raymond Chen wrote:
How about usrloc-cl?
Ray
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Klaus Darilion
Sent: 2005年11月7日 18:22
To: [EMAIL PROTECTED]
Cc: [email protected]; [email protected]
Subject: [Users] Re: [Devel] roadmap to v1.1.0
Daniel-Constantin Mierla wrote:
- 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
with failover to next server/protocol? interpret ICMP error messages
- TLS multi-domain support
- TLS configuration values to be set via a module, to keep core less
exposed
I will write a separe emails for my TLS ideas :-)
- security checks of destination addess (white/black lists)
maybe not only based on IP address, but IP address, port and protocol
(which may be also * for all ports/protocols)
[enum]
[-] - parallel/serial forking based on order and preference fields
isn't this already possible using load_gw, next_gw?
[postgres]
- connection pool
- shift to memory manager used by openser
there was a big patch by jan for ser - maybe we can use this patch.
klaus
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
