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
