Re: loadable modules ?

I think idea of having the listening http interface inside bearerbox instead
of running two executables could be usefull too.
Obviously this should be configurable ..


----- Original Message -----
From: "Nisan Bloch" <[email protected]>
To: "Stipe Tolj" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, February 21, 2002 1:08 PM
Subject: Re: loadable modules ?


> At 08:09 PM 2/21/02 +0100, Stipe Tolj wrote:
> >Oded Arbel wrote:
> >
> >yep, that brings us to 2 API architectures we should think about:
> >
> >1) module API to load-on-the-fly smsc modules (smpp, emi2, at2, etc.)
> >2) module API to load-on-the-fly sms-services (so that there is no
> >need to SIGHUP smsbox for processing)
>
>
> it might also be worth looking at splitting smsbox:
> 1. interface - at moment HTTP
> 2. processing & bearerbox connections.
>
> this way we would have an smsbox api and could bolt other frontends onto
> it. eg our applications or even something like SMPP.
>
> nisan
>
>
> >Stipe
> >
> >[email protected]
> >-------------------------------------------------------------------
> >Wapme Systems AG
> >
> >Münsterstr. 248
> >40470 Düsseldorf
> >
> >Tel: +49-211-74845-0
> >Fax: +49-211-74845-299
> >
> >E-Mail: [email protected]
> >Internet: http://www.wapme-systems.de
> >-------------------------------------------------------------------
> >wapme.net - wherever you are
>
>
>