On Mon, Mar 1, 2010 at 11:03 AM, Nikolay Kondratyev <[email protected]> wrote: > > >> > And the second thing: I'd like to have call recordings saved into a >> > database. >> > It will allow fast locating of a recording and third party access to >> > recordings. >> >> I wouldn't make putting the recordings into a database a requirement, >> but your reasons are both excellent requirements: >> >> * A documented third-party (properly access controlled) API for >> locating and retrieving recordings. > > But if not database, then what? Plain files? How much time will take to find > all calls from Peter to John made from the 1st and until 10th of December > last year? Postgres will do this easily... > Of course it depends upon how many recordings we are going to keep. > And coding is, I believe, also more convenient when using database. > The only "pro" for plain files, I can imagine, is ability to get files via, > say, ftp. But what's the use of couple of thousands files? > > Of course, this is just my opinion...
I think the point is that one should separate functional requirements from implementation details. Ranga > > Thanks and regards, > Nikolay. > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
