[xdebug-general] Re: xDebug interface for remote debugging (PHPxDebug)

From: Nathan Bruer <thegreatall[@]gmail.com>
Date: Thu, 29 Oct 2009 13:33:58 -0600

I didn't realize i sent this directly to Derick so i will post what I posted
to him:

I actually created it for another project PHPWebBug (
https://sourceforge.net/projects/phpwebbug/) which is supposed to allow
people to edit/debug files on the server though a web GUI. As I am sure you
know you are limited on how a browser can talk to servers, so I am having
the server do much of the work and the client (web browser) make frequent
calls to the server to get updates. PHPxDebug is also supposed to allow many
sessions to be ran at once without interference from other sessions
(currently they are separated in the DB, but other scripts can access/change
other debugging info, which will be addressed later).

A few years ago when this project was started (and recently started back up)
Christoph Dorn (a early developer) and I got together under a common goal to
figure out a way to allow the browser to communicate with xDebug. Christoph
has a project FirePHP (http://www.firephp.org/) which is very similar to
what my project did, so we got together and came up with a middle man script
to allow communications easier without having to do port listens and such.

The true goal of PHPWebBug is (for example) have PHPxDebug running as
administrator, and in your server panel software (like cPanel or other back
end site admin panels) would have it integrated into the software allowing
users to debug their scripts live on the server securely. (also the use for
independent use)


On Thu, Oct 29, 2009 at 1:22 PM, Christoph Dorn <christoph[@]christophdorn.com
> wrote:

> Derick Rethans wrote:
> On Thu, 22 Oct 2009, Nathan Bruer wrote:
> I thought I might let some of the community know that I (with the help of
> Christoph Dorn) have created a PHP based interface to communicate xDebug to
> client IDE's with a bit more ease...
> The project idea is that you can have the demon run on the server which
> listens for xDebug sessions, when it receives one it puts the info into a
> MySQL database and continues to check MySQL for new commands to send to
> xDebug about a specific session, and the communication between the IDE and
> xDebug can be done though another called script on the server to check the
> MySQL database and write it's commands to send to xDebug into MySQL.
> Cool to see that other people are hacking stuff on top of Xdebug. I've a
> few comments though :-) Why would this be any better than just a normal
> DBGp proxy? And does this have to offer over a pure PHP client
> implementation of the DBGp protocol?
> My interest in writing a proxy in PHP and JS client was to experiment with
> shared and automated debug sessions where a debug server built on top of
> nanoserv [1] can take instructions for the same xdebug session from multiple
> clients (or controllers) via multiple procotols. I think I had a basic
> version working when I spent time on this a year ago or more. The version
> published now does not include all the nanoserv stuff I don't think.
> I still hope to get something working in this area but am not sure if I
> will stick with PHP for the server or use JavaScript specifically narwhal
> [2].
> Christoph
> [1] - http://freshmeat.net/projects/nanoserv
> [2] - http://www.narwhaljs.org/
Received on Thu Oct 29 2009 - 20:34:07 GMT

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST