5 ************************************************
6 *** This file is a TODO. It is thus kinda ***
7 *** outdated. You know the story, right? ***
8 ************************************************
17 Document the fact that gras processes display the backtrace on sigusr and sigint
20 /* FIXME: better place? */
21 int vasprintf (char **ptr, const char *fmt, va_list ap);
22 char *bprintf(const char*fmt, ...) _XBT_GNUC_PRINTF(1,2);
25 gras_socket_close should be blocking until all the data sent have been
26 received by the other side (implemented with an ACK mechanism).
37 * Check the gcc version on powerpc. We disabled -floop-optimize on powerpc,
38 but versions above 3.4.0 should be ok.
39 * check whether we have better than jmp_buf to implement exceptions, and
40 use it (may need to generate a public .h, as glib does)
47 * Better split casual errors from programming errors.
48 The first ones should be reported to the user, the second should kill
49 the program (or, yet better, only the msg handler)
50 * Allows the use of an error handler depending on the current module (ie,
51 the same philosophy as log4c using GSL's error functions)
54 * Hijack message from a given category to another for a while (to mask
55 initializations, and more)
56 * Allow each actor to have its own setting
57 * more logging appenders (take those from Ralf in l2)
60 * Add configuration and dependencies to our module definition
61 * allow to load them at runtime
62 check in erlang how they upgrade them without downtime
65 * we may need a round-robin database module, and a statistical one
66 * Some of the datacontainer modules seem to overlap. Kill some of them?
67 - replace fifo with dynars
68 - replace set with SWAG
75 * implement the P2P protocols that macedon does. They constitute great
79 * use poll(2) instead of select(2) when available. (first need to check
80 the advantage of doing so ;)
82 Another idea we spoke about was to simulate this feature with a bunch of
83 threads blocked in a read(1) on each incoming socket. The latency is
84 reduced by the cost of a syscall, but the more I think about it, the
85 less I find the idea adapted to our context.
87 * timeout the send/recv too (hard to do in RL)
89 * multiplex on incoming SOAP over HTTP (once datadesc can deal with it)
91 * The module syntax/API is too complex.
92 - Everybody opens a server socket (or almost), and nobody open two of
93 them. This should be done automatically without user intervention.
94 - I'd like to offer the possibility to speak to someone, not to speak on
95 a socket. Users shouldn't care about such technical details.
96 - the idea of host_cookie in NWS seem to match my needs, but we still
98 - this would allow to exchange a "socket" between peer :)
99 - the creation needs to identify the peer actor within the process
101 * when a send failed because the socket was closed on the other side,
102 try to reopen it seamlessly. Needs exceptions or another way to
103 differentiate between the several system_error.
104 * cache accepted sockets and close the old ones after a while.
105 Depends on the previous item; difficult to achieve with firewalls
108 * Add a XML wire protocol alongside to the binary one (for SOAP/HTTP)
112 * Inter-arch conversions
114 - Convert in the same buffer when size increase
115 - Exchange (on net) structures in one shoot when possible.
116 * datadesc_set_cste: give the value by default when receiving.
117 - It's not transfered anymore, which is good for functions pointer.
119 - Cleanup the code (bison?)
120 - Factorize code in union/struct field adding
121 - Handle typedefs (gras_datatype_copy can be usefull, but only if
122 main type is already defined)
123 - Handle unions with annotate
125 - Handle long long and long double
126 - Forbid "char", allow "signed char" and "unsigned char", or user code won't be
127 portable to ARM, at least.
128 - Handle struct/union/enum embeeded within another container
129 (needs modifications in DataDesc, too)
133 - Check struct { struct { int a } b; }
136 * Other message types than oneway & RPC are possible:
137 - forwarding request, group communication
140 * Group communication
141 * Message declarations in a tree manner (such as log channels)?
143 [Other, more general issues]
144 * watchdog in RL (ie, while (1) { fork; exec the child, wait in father })
145 * Allow [homogeneous] dico to be sent
146 * Make GRAS thread safe by mutexing what needs to be
153 * add a version guessing the appropriate datasizes automatically
155 * log control, management, dynamic token ring
156 * a way using SSH to ask a remote host to open a socket back on me