###
### Ongoing stuff
###
+
+Document the fact that gras processes display the backtrace on sigusr and sigint
+Document XBT_LOG_EXTERNAL_DEFAULT_CATEGORY
+Document host module
+
/* FIXME: better place? */
int vasprintf (char **ptr, const char *fmt, va_list ap);
char *bprintf(const char*fmt, ...) _XBT_GNUC_PRINTF(1,2);
xbt/log.h:/** \name ERROR
xbt/log.h:/** \name CRITICAL
+gras_socket_close should be blocking until all the data sent have been
+received by the other side (implemented with an ACK mechanism).
###
### Planned
(errors, logs ; dynars, dicts, hooks, pools; config, rrdb)
[portability layer]
- * Mallocators and/or memory pool so that we can cleanly kill an actor
+ * maybe a memory pool so that we can cleanly kill an actor
[errors/exception]
* Better split casual errors from programing errors.
* Several appenders; fix the setting stuff to change the appender
* more logging appenders (take those from Ralf in l2)
-[dict]
- * speed up the cursors, for example using the contexts when available
-
[modules]
- * better formalisation of what modules are (amok deeply needs it)
- configuration + init() + exit() + dependencies
+ * Add configuration and dependencies to our module definition
* allow to load them at runtime
check in erlang how they upgrade them without downtime
Depends on the previous item; difficult to achieve with firewalls
[datadesc]
- * Implement gras_datadesc_cpy to speedup things in the simulator
- (and allow to have several "actors" within the same unix process).
- For now, we mimick closely the RL even in SG. It was easier to do
- since the datadesc layer is unchanged, but it is not needed and
- hinders performance.
- gras_datadesc_cpy needs to provide the size of the corresponding messages, so
- that we can report it into the simulator.
* Add a XML wire protocol alongside to the binary one (for SOAP/HTTP)
* cbps:
- Error handling
* gras_datadesc_import_nws?
[Messaging]
- * A proper RPC mecanism
- - gras_rpctype_declare_v (name,ver, payload_request, payload_answer)
- (or gras_msgtype_declare_rpc_v).
- - Attaching a cb works the same way.
- - gras_msg_rpc(peer, &request, &answer)
- - On the wire, a byte indicate the message type:
- - 0: one-way message (what we have for now)
- - 1: method call (answer expected; sessionID attached)
- - 2: successful return (usual datatype attached, with sessionID)
- - 3: error return (payload = exception)
- - other message types are possible (forwarding request, group
- communication)
+ * Other message types than oneway & RPC are possible:
+ - forwarding request, group communication
* Message priority
* Message forwarding
* Group communication
******
[bandwidth]
- * finish this module (still missing the saturate part)
* add a version guessing the appropriate datasizes automatically
[other modules]
* provide a way to retrieve the host load as in NWS