From c449ca0f1d53fab4e9ed0b96ab7570afc119a0a8 Mon Sep 17 00:00:00 2001
From: bdemsky <bdemsky>
Date: Sat, 15 Sep 2007 22:13:44 +0000
Subject: [PATCH] Rather than keep these in emails where we can lose them, I
 checked them in.  As we add stuff to our todo list, let's put them in this
 file.

---
 .../Runtime/DSTM/interface/ISSUESTOADDRESS    | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS

diff --git a/Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS b/Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS
new file mode 100644
index 00000000..e6e4ce9f
--- /dev/null
+++ b/Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS
@@ -0,0 +1,19 @@
+High priority list
+-------------------------------------
+1) Wrap all receive calls in loops
+  A) Perhaps the best way is to just define a macro or function call that
+does this. Look at GETSIZE macro for example...
+
+2) Check locking... There is likely a race condition on getObjType().  
+
+3) Receiving object code assume a maximum object size.  It is probably
+better to:
+  A) read size in.
+  B) allocate space for object at its final destination
+  C) read into the space
+
+Low priority list
+---------------------------------
+
+1) We shouldn't call memcopy for copying fixed-sized structs or primitive
+values...just use =
-- 
2.34.1