Re: Listen for 255.255.255.255 UDP broadcasts?

Just ran some tests and I also could not get feedback parsing for
devices on UDP broadcast addresses.

There are some issues with systems using UDP at the moment involving
sliders also, so we will get these fixed for next release.

Jarrod

On Dec 12, 3:17 pm, Jarrod Bell <jar...@guilink.com> wrote:
> I will do some tests on Monday
>
> Jarrod
>
> On Dec 12, 2:42 pm, Fiasco <dgvoll...@gmail.com> wrote:
>
>
>
> > Typo in my post there.
>
> > On Dec 11, 9:38 pm, Jarrod Bell <jar...@guilink.com> wrote:
>
> > > Should be: (.*) to capture everything.
>
> > > . represents 'any character' whilst asterix means 'zero or more times'
>
> > > Jarrod
>
> > > On Dec 12, 2:34 pm, Fiasco <dgvoll...@gmail.com> wrote:
>
> > > > Yea thats what I tried.
>
> > > > My regex for feedback is (*) to modify a text field.
>
> > > > On Dec 11, 9:22 pm, Jarrod Bell <jar...@guilink.com> wrote:
>
> > > > > Simply create a new system in System Manager, set its IP Address to
> > > > > 255.255.255.255 and UDP mode, with the port set to 8278 for both
> > > > > origin and destination ports, maintain connection checked.
>
> > > > > Then anything sent out on 255.255.255.255 on the local network will be
> > > > > received by iViewer and you parse feedback using regex (examples on
> > > > > our wiki).
>
> > > > > Jarrod
>
> > > > > On Dec 12, 2:15 pm, Fiasco <dgvoll...@gmail.com> wrote:
>
> > > > > > I want to try and get feedback from XBMC's UDP broadcasts over
> > > > > > 255.255.255.255  any thoughts on how to accomplish this?
>
> > > > > > The Broadcast functionality is not, strictly speaking, part of the
> > > > > > HTTP API because it does not use the HTTP protocol. However, it is
> > > > > > controlled via HTTP API commands and would typically be used as an
> > > > > > adjunct to the HTTP API and so is presented here.
>
> > > > > > The HTTP API is a "pull" architecture -- that means HTTP API interacts
> > > > > > with XBMC by making calls to XBMC. For an HTTP API client to maintain
> > > > > > a dynamic up-to-date display (e.g. showing the currently playing
> > > > > > song), the client must continually poll XBMC for its status.
>
> > > > > > The Broadcast facility provides the opposite approach -– XBMC makes
> > > > > > calls out (i.e. broadcasts or "pushes") to indicate significant events
> > > > > > to any clients that happen to be listening.
>
> > > > > > The Broadcast facility uses the UDP broadcast protocol with a default
> > > > > > port setting of 8278. (We chose 8278 for no other reason than that it
> > > > > > was the first unregistered port we stumbled across.) For a client to
> > > > > > receive these broadcasts, the client must register to receive them.
> > > > > > (The method of doing so will depend on the language/technology of the
> > > > > > client). XBMC broadcasts on the IP address 255.255.255.255 which is
> > > > > > the limited broadcast address. Sending a UDP datagram to this address
> > > > > > delivers the message to any host on that broadcast network. Because
> > > > > > routers never forward messages sent to this address, only hosts on the
> > > > > > connected network see these broadcasts. In other words, the client
> > > > > > must be on the local network to receive XBMC broadcasts.
>
> > > > > > XBMC broadcasts are delimited by <b></b> and may consist of a
> > > > > > numerical or textual description of the event (depening on the event)
> > > > > > followed by ";" and the level of the event (e.g. 1 or 2).
>
> > > > > > An example Windows client (with source code), XBMC Listener, that
> > > > > > listens to these broadcasts can be found here- Hide quoted text -
>
> > > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -

--

You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to commandfusion@googlegroups.com.
To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.