Rather than keep these in emails where we can lose them, I checked them in. As we...
authorbdemsky <bdemsky>
Sat, 15 Sep 2007 22:13:44 +0000 (22:13 +0000)
committerbdemsky <bdemsky>
Sat, 15 Sep 2007 22:13:44 +0000 (22:13 +0000)
Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS [new file with mode: 0644]

diff --git a/Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS b/Robust/src/Runtime/DSTM/interface/ISSUESTOADDRESS
new file mode 100644 (file)
index 0000000..e6e4ce9
--- /dev/null
@@ -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 =