aboutsummaryrefslogtreecommitdiffstats
path: root/Futures.txt
diff options
context:
space:
mode:
authorPeter Seebach <peter.seebach@windriver.com>2014-01-22 15:46:05 -0600
committerPeter Seebach <peter.seebach@windriver.com>2014-01-22 15:46:05 -0600
commit983cab2e244a69789e18285909e31014cb027d32 (patch)
treefbea08e95105e15f8a24934bdba89cd3399d2dfd /Futures.txt
parentd2c02ae49366523e1d1c5ce0d2a32624a0eedfa1 (diff)
downloadpseudo-983cab2e244a69789e18285909e31014cb027d32.tar.gz
pseudo-983cab2e244a69789e18285909e31014cb027d32.tar.bz2
pseudo-983cab2e244a69789e18285909e31014cb027d32.zip
future planning notes
Diffstat (limited to 'Futures.txt')
-rw-r--r--Futures.txt14
1 files changed, 14 insertions, 0 deletions
diff --git a/Futures.txt b/Futures.txt
index 7a39fab..284005a 100644
--- a/Futures.txt
+++ b/Futures.txt
@@ -38,3 +38,17 @@ vague implementation thoughts:
- The *at() function implementations are gratuitously complicated,
I believe because they predate the auto-canonicalization that came
with the rewritten pseudo wrappers.
+
+* Memory allocation/deallocation issues.
+ - there's a number of places where results from pseudo_get_value() are
+ strdup'd, then the originals freed, which makes no sense.
+ - there's at least one unchecked realloc() to do with the fd table.
+
+* Benchmarking/performance work.
+ - It'd be nice to get some kind of measurement of how much time is
+ going to which parts of pseudo (database access, filesystem access,
+ IPC overhead, logic, client processing, and so on).
+ - Maybe some work on finding ways to make profiling work, since I was
+ having issues getting good profiling data.
+ - Some moderately-canonical benchmarks would be nice to have for evaluating
+ the costs of various common use cases.