Re: ANN: coxpcall 1.6 (was RE: Xavate crash and coxpcall missing 'arg' variable)

[Romulo Bahiense <romulo@...>]

> it certainly doesn't look like a bug in Lua code.  for me at least,  
> LuaSocket is wonderfully stable; so it might be a compile or link  issue.

	You are a genius! I've discovered that the trouble was many flavors of 
lua.dll and lualib.dll. LuaSocket uses it's own liblua.dll and 
liblualib.dll, and I was using the LuaBinaries' lua5.dll and lualib5.dll 
(ok, there were a lost lua.dll and lualib.dll, but I don't think I was 
using it).

	To resolve the problem I just renamed my lua5.dll and lualib5.dll to 
liblua.dll and liblualib.dll, respectively.


> could you stress any of the samples from LuaSocket? (preferably one  
> that opens lots of short-lived TCP connections) if the bug doesn't  
> appear there, it would mean it's a Xavente thing.

	I've run the testsrvr and testclnt from the tests folder. Before the 
insight, it was crashing in the second or third run. After I renamed the 
dll's, everything went fine (wow, those tests eats a lot of memory : 
100MB P / 100MB V)


	Now 2 semi-off-topic questions:

1) How does Xavante handle concurrency? eg: One user is uploading a 
large file and another is browsing a web site hosted by the same http 
server at the same time?

2) Would be difficult to implement an async request? e.g.: A very slow 
request - like a database query returning many records - yelding 
periodically to not block other requests.

	That's it for now. Thanks for the help and the compile/link issue 
insight :)

--rb