RE: creating an smsc directory

I've started to work on porting the CIMD2 driver to the SMSCConn API. unfortunatly I can only do so "dry" as I have no access to a CIMD2 speaking SMSC, but I'm willing to do the coding if someone else is willing to do the debugging ;-)

--
Oded Arbel
m-Wise mobile solutions
[email protected]

+972-9-9581711 (116)
+972-67-340014

::..
Real questions asked by lawyers in real courts :
4)Was it you or your brother that was killed in the war? 




> -----Original Message-----
> From: Harrie Hazewinkel [mailto:[email protected]]
> Sent: Wednesday, August 07, 2002 5:36 PM
> To: [email protected]; dev-kannel
> Subject: RE: creating an smsc directory
> 
> 
> 
> 
> --On Wednesday, August 7, 2002 6:22 PM +0300 Kaido Karner 
> <[email protected]> wrote:
> 
> >> What about removing the old API's modules ? any votes for that ?
> >
> > +1, except cimd2 which I have to use ..
> 
> OK, what about putting the wrapper and the ones under the wrapper
> in a directory gw/smsc/wrapper
> 
> and add a configure option to enable the wrapper smsc modules.
> 
> I know this would require you, Kaido, to have an extra option for the
> configure phase. But it cleans up the modules used by others.
> 
> In the long term it would be nice to have a configure option
> that specifies which of the SMSC modules you need.
> (The wrapper could be one of those, and cmid2 should maybe be ported
> to smscconn API)
> 
> 
> 
> Harrie
> 
> Internet Management Consulting
> mailto:[email protected]                http ://www.mod-snmp.com/
> -------------------------------------------------------------------
> Author of MOD-SNMP, enabling SNMP management to the Apache server.
> 
> 
>