On 05/07/12 20:19, Ajay Garg wrote:
Hi all.
I ran into a issue, as described at
https://bugs.freedesktop.org/show_bug.cgi?id=51501
This behaviour is not a bug. It's a side-effect of how MDNS is
(intentionally) designed.
Your bug report states that the callback is not called. It will in
Hi,
I recently ran into a bug when advertising a service on both IPv4 and
IPv6. In this particular instance the application (for legacy reasons)
opens v4 and v6 sockets separately, and hence ends up with different ports.
I then attempted something like this (excuse the pseudo code):
===
On Tue, Jul 10, 2012 at 4:55 AM, Patrick Oppenlander
pattyo.li...@gmail.com mailto:pattyo.li...@gmail.com wrote:
On 05/07/12 20:19, Ajay Garg wrote:
Hi all.
I ran into a issue, as described at
https://bugs.freedesktop.org/show_bug.cgi?id=51501
This behaviour
On 11/07/12 01:17, Ajay Garg wrote:
So, perhaps a client notification *should* get notified, once the
transient-resolved-records expire??!!
This doesn't help as these records always expire after two minutes. They
are not refreshed unless another resolve is requested.
Patrick
On 01/09/13 22:24, E-J van der Linden wrote:
A windows 7 system with ipv6 enabled, with the latest bonjour sdk installed
does not see the ipv6 device nor the published services.
If I run my Linux device on IPv4, the PC with bonjour can see the ipv4 devices
and published services on the
