yeah - that's the rub - we're not about to spend any development resources to implement adding an extra socket listener, so we're stuck with having with eclipse having to listen for the connections. not to say someone else in a similar situation wouldn't want the mechanism you described - but given there are so few implementations of the dbpg engine for perl (by my count, there is a total of 1) and the other languages as well, this may only be a useful feature for you for some time to come given the extra level of effort that would be required on the user's end to make it work.
No the same source lives on both places , And when the debugger is connected it is compiled with linenumber info and the debugger (so a debuggable script is generated instead a compiled or interpreted)
We have our own "hot swap" implemented so if you save a script in eclipse we push that to the client in our own way (separate of the _javascript_ debugger) and it is compiled again
Let me first figure out what things i can commit pretty harmless so that i can cleanup my outstanding code because i have quite a lot of changes (bug fixes and improvements like remote debug)
Then i can send you a patch so that you can also quickly look at it if you want. And see how we integrate it correctly and nicely reusable for everybody.
looking forward to this - if you haven't already, perhaps you could try out the firefox plugin and see how that works that way you'll be able to give insight from both sides of how this needs to be supported.
