Re: Implementing Frontend/Backend Protocol TCP/IP
От | Raimon Fernandez |
---|---|
Тема | Re: Implementing Frontend/Backend Protocol TCP/IP |
Дата | |
Msg-id | 9A9F2678-36B9-42A2-91B2-69076065E8EB@montx.com обсуждение исходный текст |
Ответ на | Re: Implementing Frontend/Backend Protocol TCP/IP (John DeSoi <desoi@pgedit.com>) |
Ответы |
Re: Implementing Frontend/Backend Protocol TCP/IP
Re: Implementing Frontend/Backend Protocol TCP/IP |
Список | pgsql-general |
Hello, As this thread it's alive, I'm going to ask more specific questions: After sending the satartup sequence, I receive the paramlist. I don't need to send Authentication as I'm using a Trust user, for making things easier. I receive string data, I suppose it's text data. I can parse the data received, search for a B. I don't know if it's better to transform the data into Hex. After the S I found thre char(0) and later the size of the packet, and later the name + char(0) (separator between value and parameter), the parameter, and so on. Why I found those three char(0) after the S and before the packet length? Or it's because the Int32 that has 4 bytes ? thanks, regards, raimon Documentation: ----------------------------------------------------------------------------- ParameterStatus (B) Byte1(’S’) Identifies the message as a run-time parameter status report. Int32 Length of message contents in bytes, including self. String The name of the run-time parameter being reported. String The current value of the parameter.
В списке pgsql-general по дате отправления: