The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: xFx Pop3 issues


  • Subject: Re: xFx Pop3 issues
  • From: Stuart Booth
  • Date: Sun, 14 Mar 2004 22:46:00 +0000

On Sun, 14 Mar 2004 20:39:35 +0000, James Traynor <<a
href="/group/xap_automation/post?postID=W4q1ClT452kJB6pB3pvrk2ZuWwpbHBicZJajkCfjB3jaTRo2p8n8FaFZ1mUMYJ9BgAsUC9k">james@m...</a>>
wrote:

>Also noticed that the xfx apps as servies don't generate any hearbeat
>stopped messages when the service is stopping.

Just tested a new SlimServer Connector build as a service and it does
send out that message. Which ones do you fail to see xap-hbeat.stopped
messages coming from? I think they maybe older versions that I've not
updated on the site yet, as this was a change I made to xFx reasonably
recently (ish).

The POP3 app has been heavily revised since the current public version
was uploaded last year. There is a still an occasional bug that I
haven't got to tracking down yet so I've not released this latest
build. Plus it needs a configuration GUI ala the SlimServer Connector
which I have yet to implement for it.

I'll get to the other queries you raised shortly. I'm almost done with
the jobs required of me tonight. Hope that's okay!

S
--
Stuart Booth <<a
href="/group/xap_automation/post?postID=2mC__4ml_mwcN_QRuSIfKHPCpf_l0qvKtHwxzooUSEUwEGsA5IkE50Vd7Msn4uoX1FtT3fxSCZewFuGqioQM">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>





xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.