What about the mysql store patch from Alejandro?

Can it be also added to main head?  I've tested it and work flawlessly.

Regards

Alvaro


|-----------------------------------------------------------------------------------------------------------------|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
              Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com



On Mon, Jan 26, 2009 at 11:21 AM, Alejandro Guerrieri
<[email protected]> wrote:
> And what happens if processors use different versions? A PANIC condition or
> some sort of error?
>
> It would definitely help tracking the source of the problem, though wouldn't
> solve the fact that the formats are incompatible. If you upgraded the
> binaries to an incompatible version while there were messages on the store,
> you won't be able to load them again.
>
> Assuming that the changes are minor (e.g., no new mandatory fields added)
> store_tools could be extended to provide some means of "abstract" file
> format that could be imported/exported between versions to help migrate the
> data (export -> upgrade -> import).
>
> Regards,
> --
> Alejandro Guerrieri
> [email protected]
>
>
>
> On 26/01/2009, at 16:38, Stipe Tolj wrote:
>
>> Alejandro Guerrieri schrieb:
>>>
>>> I've made a new kannel utility to be able to manipulate the store
>>> file/spool. It's called "store_tools" and it allows to list, delete and
>>> export messages from the store into other formats (it could be used to
>>> move messages from file to spool and back).
>>>
>>> Here's more info and the patch:
>>>
>>> http://www.blogalex.com/archives/72
>>>
>>> Please try it and consider adding it to the test folder so it becomes
>>> part of the main tree.
>>
>> cool, will have view... thanks Alejandro for the effort. Applause from the
>> audience please! :)
>>
>> Another thing I'd like to raise in this "scope" of the store subsystem ->
>> versioning.
>>
>> At the moment we're pretty incompatible when a store file or spool is used
>> on an
>> updates set of binaries, this includes also the inter-box communication
>> between
>> bearerbox and smsbox connections if their "msg struct" differ.
>>
>> I'd like to have this handled more gracefully, i.e. by versioning the msg
>> struct
>> with a "magic cookie header", so that the participating processors of the
>> msg
>> struct "know" with what they are dealing. I had the magic cookie header
>> format
>> as used in the Apache module API in mind.
>>
>> Any comments, suggestions?
>>
>> Stipe
>>
>> --
>> -------------------------------------------------------------------
>> Kölner Landstrasse 419
>> 40589 Düsseldorf, NRW, Germany
>>
>> tolj.org system architecture      Kannel Software Foundation (KSF)
>> http://www.tolj.org/              http://www.kannel.org/
>>
>> mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
>> -------------------------------------------------------------------
>>
>
>
>

Reply via email to