File: TODO

package info (click to toggle)
skstream 0.3.9-3
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 1,896 kB
  • ctags: 535
  • sloc: sh: 10,997; cpp: 2,605; makefile: 64
file content (54 lines) | stat: -rw-r--r-- 2,423 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
::underflow seems to involve a full copy of the data - copy bad!
see "move receivd data..."(sic)

Add return status codes to ->open() functions.

Remove the BEOS conditionals.

A datagram implementation requirements:

  The application must be able to control the datagram. ie. prevent the stream
  from sending a datagram arbitrarily, and having a function to send the
  datagram. This is going to need a way to specify the target. The receiving
  implementation is going to need a way for the application to tell where
  the data came from.

  Need to sort out what to do about socket addresses. Should a class
  encapsulate addresses, and address sets (as returned by getaddrinfo()).

  Some more difficult features are things like the need to efficiently
  output data destined for many clients. Current server implementations
  involve serialising the data once each time it is sent to a client (on
  stream sockets). In datagram sockets, if we can somehow agregate all
  the clients that are listening to the same codec, we can serialise
  once, and transmit to all of them.

  On a purely worldforge note, we will need to add features to Atlas-C++
  to handle stuff. Need to add the functionality to Atlas-C++ to handle
  many more directives at the negotiation phase - arbitrary directives
  need to be handled by the client code.

a datagram server and stream are not really separate functions. Try and
sort out necessary features in the stream. In particular, need to flag
whether it sould accept for anywhere, or only one particular place.
It must be necessary to set target v. efficiently, which may require
an abstraction of network address.
Use basic_socket_stream constructer argument to initialise protocol.

Clean out in_peer and out_peer. Sort out startup, as it needs to be static.

Need to sort for once and for all the issue of streambuf objects
being part of the superclass.

Fix up ping.cpp to use provided features to do low level stuff, adding
features to the library if necessary.

Reformat all the code according to the standard WF style.

tcp_socket_stream is passing a reference up to the next class to be
constructed before the stream buffer object referred to has been constructed.
This results in a "Conditional jump or move depends on uninitialised value"
error from valgrind.

Use a -DHAVESKSTREAMCONFIG_H to tell the code to include the genereated header, else
include a pre-defined one.