On Montag, August 11, 2003, at 12:51 Uhr, Stipe Tolj wrote:
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?
why huge? entries in this list should not be kept too long.
an alternate way of API would be to use a MySQL DB directly as secondary solution.
But this brings us to a routing issue in general.
Andreas Fink Global Networks Switzerland AG
------------------------------------------------------------------ Tel: +41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/� [EMAIL PROTECTED] ------------------------------------------------------------------
