Hi, > I was very surprised, that trouble with connection to Erlang frozen > ErlIDE and Eclipse GUI as well. > Is ErlIDE single-threap app ?
Mostly, yes. The problem is really that there isn't yet a good error handling. If any object needs to access the Erlang backend, it has to get a handle to the said backend - but getting it involves starting the node and waiting for it to go up... A better way to handle this is to return a proxy object that does nothing and wait for the node in the background. However, I'm not sure what clients should do while the backend is unavailable... Suggestions are welcome. > And seeing how many java threads/processes Eclipse launches, i can only > wonder, whay could not Eclipse protect itself by launching each plugin > in separate thread? At least those that are not stable releases :) You would then get plenty of concurrency issues, because not all Eclipse platform is thread-safe. It is already difficult to remember that some callbacks are executed in different threads. regards, Vlad ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Erlide-devel mailing list Erlide-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/erlide-devel
