<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Lucida Console'; font-size:9pt; font-weight:400; font-style:normal;">On Dienstag, 23. Juni 2009, Raśl Alexis Betancor Santana wrote:<br>
> > >> It would provide access to database (internal database API) not<br>
> > >> management API. I want alias_db, auth_db, domain, group, usrloc etc.<br>
> > >> to work directly with HTTP/REST layer.<br>
> > ><br>
> > > Why not just provide an HTTP/REST interface to the database, then?<br>
> ><br>
> > What if I have database, but it is not Mysql/Postgres/Oracle ?<br>
><br>
> Well, an ODBC connector could be created insted of HTTP/REST one, that will<br>
> have a very high performance penalty.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Hi Raśl,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>there is already a module that connects to ODBC drivers, "db_unixodbc".<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> > What if one have more complex setup than plain tables (subscriber/aliases<br>
> > and so on)? What if one have some CRM or ERP system without direct data<br>
> > access but with some API instead?<br>
><br>
> If you have such "complex" scenario, you should develop a way to dump your<br>
> CRM/ERP data into Kamailio structures and not viceversa.<br>
><br>
> > With REST/HTTP layer we can adapt any complex API to SER database API.<br>
><br>
> NO, what you do is to add another layer, with a very high performance<br>
> penalty and also with it owns weakness.<br>
><br>
> > In our project we use distributed database without plain tables and plain<br>
> > select/update access.<br>
><br>
> Think about what Kamailio/Sip-Router needs and if it's better to develop an<br>
> interface between Kamailio -> YourSystem or it's better to develop an<br>
> interface between YourSystem -> Kamailio.<br>
> I think that the second approach would be better.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I can't really comment if its make sense to use such a translation layer as i don't know the system and the exact requirements of the original poster, even if i also like to keep it simple. But if such a translation module is useful to some group, the created code is understandable, documented and maintainable then i don't see a real reason that we this should not be accepted in our repository [1]. Of course it should be implemented in a general way, that it can be changed with some configuration to adapt to different URL schemes, for example, like the SER ldap module.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Henning<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>[1] http://www.kamailio.org/mos/view/Contributions/</p></body></html>