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: Re: Developing with lib v4...


  • Subject: Re: Re: Developing with lib v4...
  • From: Tom Van den Panhuyzen <tomvdp@xxxxxxxxx>
  • Date: Thu, 22 Sep 2005 20:04:09 +0200
  • References: <dgumie+ca70@eGroups.com> <4332eeb1.6d1d7827.5238.2237SMTPIN_ADDED@mx.gmail.com>

The older xpllib code forgets to free its port after sending a
message.  Could be that.

Tom


On 9/22/05, Tony Tofts <tony@xxxxxxx> wrote:
> > (BTW, why
> > does xPLHal bind to 30-odd UDP ports?)
>
> As douglas adams would probably say "42", or who knows?
>
> The only ports it binds are the xpl and xap base ports (for hubs) and
it's
> own connection to the xpl hub, there's no other code in xplhal that
binds
> any other udp port... So why more than 3 is bound is anyone's guess
>
> BTW mine shows 82 ports (after a reboot)
>
> Regards
> Tony
>
>
>
> xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
> http://www.xpl.myby.co.uk
> To Post a Message: ukha_xpl@xxxxxxx
> To Subscribe:  ukha_xpl-subscribe@xxxxxxx
> To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx
>
>
>
> ________________________________
> YAHOO! GROUPS LINKS
>
>  Visit your group "ukha_xpl" on the web.
>
>  To unsubscribe from this group, send an email to:
>  ukha_xpl-unsubscribe@xxxxxxx
>
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>  To unsubscribe from this group, send an email to:
>  ukha_xpl-unsubscribe@xxxxxxx
>
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
> ________________________________
>



xPL Main Index | xPL Thread Index | xPL 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.