----- Original Message -----
From: "Kym Kovan" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 05, 2001 12:03 AM
Subject: Re: [iMS] POST 2.0.6 beta 5 feedback
> Hi Howie,
>
> Slow reply, lunch and a visit from our finance guy got in the way (the cost
> of Cisco routers is scary these days) :-)
>
:-(
> > > Just make the file format nice and easy to parse out with ColdFusion :-)
> > >
> >
> >Example? The queue only holds the next delivery attempt date/time and the
> >name of the control file...
>
> OK, that is simple then. All you need is a decent, non-ambiguous delimiter
> between the datetime and the name.
>
A comma, perhaps?
> I'm just thinking back to when we used to get control files that were never
> read, with a:
>
> Start=20010605122201
> Next=20010605122201
>
> that just sat there. Does the control file have the original time or just
> when it thinks the next delivery is?
>
The start is the time the control file was created and the next is the date/time of
next delivery attempt.
> As an aside that file I copied the times from is the original of a "95er".
> We are still getting them occasionally with a control file in the queue
> that is like so:
>
> [Delivery]
> Start=20010605122201
> LastWarning=20010605122201
> Next=20010605122201
> Priority=5
>
> and nothing else in the file, ie its a bit short :-) (95 is the length of
> the file). We have an engine that parses the queue folder every so often
> and deletes these and then the original control file gets copied across again.
>
That shouldn't happen with the latest servers...
> > > Following on with your second post it probably would be a good idea to
> > > (variably) restrict the size of the dump. Would it be possible to time sort
> > > the queue and then have a startrow/maxrows type of thing? Maybe make the
> > > semaphore file have content with the parameters in it.
> > >
> >
> >The queue is sorted :-)
>
> I had a feeling it was :^)
>
> >I'm not sure how to do the startrow thing because the queue is dynamic so
> >if you view the first 20 records, for example, and then
> >decide to view the next 20 then the queue will more than likely have
> >changed by then.
>
> I was just thinking of a mechanism to keep the load off the server whilst
> doing this. Possibly wanting to read the end of the file, not the
> beginning, that sort of thing.
>
Well...I would not be printing out the POST Server queue unless debugging...I mean,
there is no mail server on the planet that gives
this but I would not overuse it...
> >Also, I would allocate this function to a
> >background process that would not print this out immediately anyway.
>
> Fair enuf.
>
OK then.
Regards,
Howie
> --
>
> Yours,
>
> Kym
>
>
> ========================================================================
> This list server is Powered by iMS
> 'The Swiss Army Knife of Mail Servers'
> --------------------------------------
> To leave this list please complete the form at
> http://www.coolfusion.com/iMSSupport.cfm
> Need an iMS Developer license? Sign up for a free license here:
> http://www.coolfusion.com/iMSDevelopers.cfm
> List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
> ========================================================================
>
========================================================================
This list server is Powered by iMS
'The Swiss Army Knife of Mail Servers'
--------------------------------------
To leave this list please complete the form at
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license? Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================
