Re: Re: SliMP3 Connector as a Windows Service now available

[Stuart Booth]

On Sun, 12 Oct 2003 18:16:22 -0000, "max_adamiec"
<<a
href="/group/xap_automation/post?postID=Z3x92wnWPxEGXsHgh98VW6TFMvgMxFNWZfklsWLTGs96AXHtax6kVl2iuVVdIN30cL-9YyAhQ7ktN2yrNg">max@v...</a>>
wrote:

>I've updated to the new email osd service, pop3 service, and the
>slimp3 service and everything appears to be working as expected.
>
>Had an issue with the slimp3 connector service not starting on
>bootup, reinstalled the service and all seems fine now.

Oh dear. Let me know if that persists and I'll tell you how to get
some trace output out of the thing, which could help us.

I tend not to use the Service versions too much yet as I'm constantly
taking things up and down for testing purposes and a console app is
(slightly) easier to stop. 2 SliMP3 connectors on the xAP Network
tends to confuse things for instance, although I can target my test
messages properly now so I can probably work around that.

BTW, earlier this afternoon I added a threaded message queue to the
SliMP3 Connector so that each message gets its fair share of screen
time. All other functionality remains accessible whilst messages are
being displayed. It's been running fine for most of today but I'm
giving that some testing time here first. Shout if you want a preview
beta build to test (means yet more uninstalling/reinstalling though)
as I think this will be particularly useful for you.

Next I'm going to see what I can do about the double height messages.

Let me know if there are any other configuration options needed to get
the kind of email display you want. If you find it useful, others
almost certainly will too.

S
--
Stuart Booth <<a
href="/group/xap_automation/post?postID=ArHmzEo0V0wpgNaLNz6NYoyfxxJhbA32xyhDxiPGmagKabsX81U3FIOJ4dxfjRY9SXANWlF66CFvmeiq9p4">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>