Andres, Thanks for the clarification and no worries on the missing "not".
I actually confused you by using "CGI" in a very generic sense meaning simply that a web server would get a request and then run short-path dive on these large Lua tables. Remember that my Lua table (Graph) is huge, persistent, and being updated constantly….in fact it's a batch process that runs forever…. So where I'm still lost is that I don't understand how Copas, Xavante, FastCGI or any other technology is able to read (in parallel) a Lua table that exists in my dedicated Lua memory process. Please forgive my attempt at clarification if you are already clear those points but I just wanted to confirm that we're on the same page before I did a deep dive on the products you have pointed me to. If you can confirm that either Copas or Xavante would (with customization) be able to gain read-only access to this in-process Lua table, then I'll dig into those products and figure out the details to make my short-path code run from there. I'm not a low level programmer so perhaps this is easy stuff and I just don't realize how easy it is? Thanks again. Dewey On Mar 7, 2010, at 1:22 PM, Andre Carregal wrote: > My advice would be to use a persistent process like FastCGI, but if > you end up needing to use CGI, the deamon could be written in Lua if > you wanted. It would be basically a socket listening server that would > accept requests, eval the short path using the in memory data > structure you have, and reply with the appropriate response. > > In that direction, you may check Copas to see if it would work for > you, or use Xavante as a web server with persistent states and use > HTTP as the protocol for your requests (for example in JSON or simply > a serialized Lua table). _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
