|
||||||||||
PREV NEXT | FRAMES NO FRAMES |
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
Why does this (control point) protocol implementation ignore anything but root device notification messages? The UDA 1.0 spec says that if a device comes online, it will send out dozens of advertisement messages. |
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
|
|
||||||||||
PREV NEXT | FRAMES NO FRAMES |