[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-krn-devel
Subject:    Re: KRN and KMail ?
From:       Stefan Taferner <taferner () alpin ! or ! at>
Date:       1997-08-05 16:56:38
[Download RAW message or body]

At 10:46 05.08.97 -0300, you wrote:
>
>Unifying the queues would be easier if we had only one posting class, 
>since now the app sending it is not the one that got the user command.
>It could, however, be stored in an auxiliary file?
>Something like 
>
>SomethingThatIdentifiesAMessage yes no
>
>where the first yes means "yes, mail it", and the second no means "no, 
>not news".

I am still a bit undeceided about this. It would require a special type
of message folder. The other case with the two queues can cope with
every type of folder by the cost of double storage use in the case where
you send messages to news and mail.

Does it make a big difference to check two queues instead of one ?
I think not.

>> class KPoster
>> {
>>   void post(KMessage*, short sendNow=-1);  // 0=no, 1=yes, -1=use default
>>   virtual void sendNow(void);
>>   const char* type(void) const;  // returns "news" or "mail"
>> 
>>   // some configuration stuff follows here, e.g. the folder where msgs
>>   // are queued and so on.
>> }
>> 
>> 
>> sendNow() sends all queued messages depending on the type of the
>> poster.
>
>Hmmm... I would change it to
>
>sendNow(int flush=-1) //1 do it, 0 don't, -1 default

That means sendNow(0) does nothing ?
Hmm... not that obvious IMO.

>And give the user an option of whether he should flush the queues when
sending
> the message? (flushing it can be time consuming)

The user has this option because he can configure the mail senders to
online or offline by default.

He should also be able to override this behaviour when composing a particular
message.

>
>Ok, I like it. It's really no difference. And I can encapsulate those two 
>classes in one that works the way I like it! Just kidding ;-)

No, you are right. That would not matter. I just have split them to make the
core obvious.

>> B-))
>> And drop all duplicated postings on the way of course.
>> I like your idea.
>
>Of course. Krn works exculsively by Message ID, so unless it's a 
>multipost, it should only appear once. 

Yes.

Regards, Stefan

[prev in list] [next in list] [prev in thread] [next in thread]