Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

## Uses of Class
org.teleal.cling.protocol.ReceivingAsync

Packages that use ReceivingAsync
org.teleal.cling.protocol |
org.teleal.cling.protocol.async |
org.teleal.cling.protocol.sync |

Uses of ReceivingAsync in org.teleal.cling.protocol

Subclasses of ReceivingAsync in org.teleal.cling.protocol
`class` | `ReceivingSync<IN extends StreamRequestMessage,OUT extends StreamResponseMessage>`

Methods in org.teleal.cling.protocol that return ReceivingAsync
`ReceivingAsync` | `ProtocolFactoryImpl.createReceivingAsync(IncomingDatagramMessage message)`
`ReceivingAsync` | `ProtocolFactory.createReceivingAsync(IncomingDatagramMessage message)`

Uses of ReceivingAsync in org.teleal.cling.protocol.async

Subclasses of ReceivingAsync in org.teleal.cling.protocol.async
`class` | `ReceivingNotification` The following was added to the UDA 1.1 spec (in 1.3), clarifying the handling of messages: "If a control point has received at least one 'byebye' message of a root device, embedded device, or service, then the control point can assume that all are no longer available." Of course, they contradict this a little later: "Only when all original advertisements of a root device, embedded device, and services have expired can a control point assume that they are no longer available." This could mean that even if we get 'byeby'e for the root device, we still have to assume that its services are available.
`class` | `ReceivingSearch`
`class` | `ReceivingSearchResponse`

Uses of ReceivingAsync in org.teleal.cling.protocol.sync

Subclasses of ReceivingAsync in org.teleal.cling.protocol.sync
`class` | `ReceivingAction`
`class` | `ReceivingEvent`
`class` | `ReceivingRetrieval`
`class` | `ReceivingSubscribe`
`class` | `ReceivingUnsubscribe`

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

Copyright © 2010 Teleal GmbH, Switzerland. All Rights Reserved.