1 This part of the documentation is for the new tcp elements:
7 which are created to replace the old tcpsrc/tcpsink
11 Use these tests to test functionality of the various tcp plugins
13 * server: nc -l -p 3000
14 client: nc localhost 3000
15 everything you type in the server is shown on the client
16 everything you type in the client is shown on the server
18 * server: nc -l -p 3000
19 client: gst-launch tcpclientsrc protocol=none port=3000 ! fdsink fd=2
20 everything you type in the server is shown on the client
22 * server: nc -l -p 3000
23 client: gst-launch fdsrc fd=1 ! tcpclientsink protocol=none port=3000
24 everything you type in the client is shown on the server
26 * server: gst-launch tcpserversrc protocol=none port=3000 ! fdsink fd=2
27 client: gst-launch fdsrc fd=1 ! tcpclientsink protocol=none port=3000
32 - implement DNS resolution
36 This is the old documentation for the original tcpsrc/tcpsink elements.
38 * What is TCP src/sink?
40 solution, like icecast or realaudio or whatever.
41 But the future RTP plugins shall not do the actual transmission/reception
42 of packets on the network themselve but the Application developer would be
43 encouraged to use either the TCP or the UDP plugins for that. UDP would be
44 used mostly but there could be situations where TCP would be the only
45 available choice. For example streaming accross firewalls that do not
50 Even given our modest ambitions, the current code doesn't handle
51 caps negotiation robustly.
55 The caps nego should do bi-directional negotiation.
57 Perhaps this plugin can be the example of how to do caps negotiation
58 via a point-to-point protocol.
61 Wim Taymans <wim.taymans@chello.be>
62 Joshua N Pritikin <vishnu@pobox.com>
63 Zeeshan Ali <zak147@yahoo.com>