> An HTTP 'callback' sounds good as an initial implementation. Generic and > flexible.
yep. I'm also in a favor of this. Where API should be very simplified like: earerbox calls http://www.foob.com/?msisdn=<msisdn> and that HTTP server replies with either an smsc-id as body/header(?!) or nothing (indicating he doesn't know where to route). The question is would we do some kind of internal caching for this? This would speed up things drastically. Maybe using a *huge* Dict hash? Has anyone used huge Dict hashs? Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 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
