[xdebug-general] Re: Proxy

Hi Derick, all.

I had a bit of time, and rewrote the proxy so it handles sockets in a
nonblocking way.
Also the code is cleaned up a bit, but still a procedural mess. q:)

Best regards,
-Zobo

Derick Rethans wrote:
> On Wed, 8 Aug 2007, Damjan Cvetko wrote:
>
>
>> I'm sending you the code directly, as I don't want to trash the list with it.
>>
>
> (I'm cc-ing the list again - hope you don't mind)
>
>
>> The code is a real mess, as it was planned for a base of a C application. I'm
>> sure it can be blocked (network wise) as I was stuck not using threads or
>> other fancy network methods. If you think it has potential to bundle this
>> proxy with the package, I'll rewrite parts of the code to make it more robust
>> (better low level network handling and perhaps true nonblocking sockets). The
>> -m parameter (multiple sessions) is also not handled at all.
>>
>
> Thanks for sending it, I'll give it a spin a bit later this week, and
> then also dive a bit more in the code.
>
>
>> It sometimes leaves my dbgp client in a non finished socket state and I cant
>> figure why. If you have a clue to why I'd appreciate it.
>>
>
> Because it's sometimes, I wouldn't know :)
>
>
>> Another question. DBGP specification doesn't say anything about a reply to
>> proxystop command. Currently the implementation does not return anything.
>>
>
> Hmm, you are right. I would assume it should return this though:
>
> <proxystop success="1"/>
>
> regards,
> Derick
>
>