Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-22 Thread Stipe Tolj
Alexander Malysh wrote: > > Hi Bruno, > > can you please first post such radical changes to ML before you commit these? > It would be great first to review this patch... We are in pre-release phase > now (imo)... or ? agreed *fully* here! Bruno, you *have to* ask for votes in case commiting cha

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-21 Thread Alexander Malysh
Am Sonntag, 20. Juli 2003 15:52 schrieb Oded Arbel: [snip] > > > then it's a bug and must be fixed! > > well.. FYI: the bug is fixed now... [snip] -- Best regards / Mit besten Grüßen aus Düsseldorf Dipl.-Ing. Alexander Malysh ___ Centrium GmbH Vogelsan

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Oded Arbel
On Sunday 20 July 2003 15:48, Alexander Malysh wrote: > > > then we should change Counter, in order to be able to handle long > > > long... > > > > What counter ? > > Counter is used to generate msg id ... > Ok, i see now... Heh , do you have any situations that message id is not > set? yes.

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Alexander Malysh
On Sunday 20 July 2003 13:51, Oded Arbel wrote: > On Sunday 20 July 2003 15:06, Alexander Malysh wrote: > > On Sunday 20 July 2003 13:23, Oded Arbel wrote: > > > On Sunday 20 July 2003 14:39, Alexander Malysh wrote: > > > > I can not undestand , why this change should be done? We use msg id > > > >

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Oded Arbel
On Sunday 20 July 2003 15:06, Alexander Malysh wrote: > On Sunday 20 July 2003 13:23, Oded Arbel wrote: > > On Sunday 20 July 2003 14:39, Alexander Malysh wrote: > > > I can not undestand , why this change should be done? We use msg id > > > only for our internally purposes and msg id has nothing t

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Alexander Malysh
On Sunday 20 July 2003 13:23, Oded Arbel wrote: > On Sunday 20 July 2003 14:39, Alexander Malysh wrote: > > I can not undestand , why this change should be done? We use msg id only > > for our internally purposes and msg id has nothing todo with provider msg > > id... Can you please explain why it

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Oded Arbel
On Sunday 20 July 2003 14:39, Alexander Malysh wrote: > I can not undestand , why this change should be done? We use msg id only > for our internally purposes and msg id has nothing todo with provider msg > id... Can you please explain why it should be needed ? Several providers required that we r

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Alexander Malysh
Hi Bruno, can you please first post such radical changes to ML before you commit these? It would be great first to review this patch... We are in pre-release phase now (imo)... or ? On Sunday 20 July 2003 01:06, Bruno Rodrigues wrote: > Hello to all. > > After several warnings but no one chang

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Alexander Malysh
Hi Oded, I can not undestand , why this change should be done? We use msg id only for our internally purposes and msg id has nothing todo with provider msg id... Can you please explain why it should be needed ? Have you sooo much traffic running on your bearerbox, so that 32bit not enough ? and

Re: [ANNOUNCE] Compatibility breaking in next release

2003-07-20 Thread Oded Arbel
On Sunday 20 July 2003 02:06, Bruno Rodrigues wrote: > Now it's the right time to fix what's wrong, just before releasing a new > version ;) Speaking of compatibility breaking - I'd like to suggest a more radical change : changing the message ID used in kannel internal messaging to 64 bit length

[ANNOUNCE] Compatibility breaking in next release

2003-07-19 Thread Bruno Rodrigues
Hello to all. After several warnings but no one changing the code, I'm picking up the job and finally fixing my own bug. Very soon (I have already finished the code but I'm still testing and documenting) I'll commit a patch to fix inconsistences in cgi parameters (which were primarly caused by me