[hydra-dev] Hydra definition

[Marc Blanchet]

- good!, let me roll the ball!
- this first cut is high-level with many "such as". great. (no criticism 
intended.)
- as an engineer, I prefer down to the bottom technical 
requirements/features with some priorities or short/medium/long term goals.
- to me, hydra is a very different beast if, for example (just for example):
  + it has just the SIP suite, or all the other protocol suites. 
Therefore, a clear list of protocols is needed.
  + it is or it is not a TDM node.
  + ...

That (technical requirements/feature list with ordered priorities) would 
help me (maybe only me?) understand what we are trying to achieve.

(right now, I've only saw commits related to a generic framework. (no 
criticism intended). It looks far from what would carry a phone call. So 
the commits do not help me neither to understand what we are trying to 
achieve.)

Marc.

Le 10-06-08 12:50, Ken Hunt a écrit :
>
> All,
>
> Based on discussions in previous e-mails, I have posted a new page on the wiki (clearly marked as DRAFT) as a place for us to define what Hydra is, it's goals, and so forth. I have attempted to get the ball rolling.
>
> Have a look and share your thoughts.
>
> https://myth.asterisk.org/wiki/display/TOP/Hydra+Defined
>
> Cheers,
> Ken Hunt
>
>
> _______________________________________________
> Project Hydra Development Discussion List
> NOTE: All content you receive from this list is should be treated as confidential.
>
> To UNSUBSCRIBE or update options visit:
>     http://lists.digium.com/mailman/listinfo/hydra-dev


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca