Re: [PATCH] store spool directory support

"Vincent CHAVANIS" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <03bb01c6f8e7$e472cb20$9600a8c0@vince>
The link provided is not reachable.
Could you please, attach the patch to the ML?

Vincent.

--
Telemaque - 06560 SOPHIA-ANTIPOLIS - (FR)
Service Technique/Reseau - NOC
Developpement SMS/MMS/Kiosques
http://www.telemaque.fr/
[email protected]
Tel : +33 4 92 90 99 84 (fax 9142)
----- Original Message ----- 
From: "Alexander Malysh" <[email protected]>
To: <[email protected]>
Sent: Thursday, October 26, 2006 11:50 AM
Subject: Re: [PATCH] store spool directory support


> Hi,
>
> any objections or I go to commit this patch?
>
> Am 17.10.2006, 18:20 Uhr, schrieb Alexander Malysh <[email protected]>:
>
>> Hi,
>>
>> please find at https://olek.homeip.net/~alex/store-spool.patch patch 
>> that adds additinaly support for store spool directory.
>> I added two new config options:
>> 'store-type' - allow us to define which type to use (file, spool)
>> 'store-location' - allow setting either file or spool location
>>
>> Option 'store-file' is deprecated but still supported with a warning 
>> that two above options should be used.
>> By default if no 'store-type' defined store file is used.
>>
>> Advantages of the store spool is:
>> 1) each message stored as one file, so it's easier to drop one specific 
>> message from the queue
>> 2) no need to have queued messages twice in the memory
>> 3) no locking required -> no race conditions as is the case for store 
>> file
>> 4) some other that I don't know yet :)
>>
>> Please test it and give me feedback.
>>
>> Note: you should use store spool on the drive with jurnaled filesystem 
>> otherwise it's really slow (best results I reached with reiserfs).
>>
>> Note2: I was unable to upload patch to kannel.org so if my devel machine 
>> not reachable don't worry just retry later.
>>
>
>
>
> -- 
> Thanks,
> Alex
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.