[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    [GENERAL] Merged Model for libpq
From:       Annamalai Gurusami <annamalai.gurusami () gmail ! com>
Date:       2011-03-31 16:46:17
Message-ID: BANLkTikpi_Y5Ti1hrZpd8OJ3HTQBLMQWCg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (text/plain)]

Hi All,

I would like to know about the best approach to take for providing a merged
model of libpq library.  When I say "merged model" it means that the client
and server would be running as a single process.  A single client libpq
application can be linked to either the client-server libpq library or
merged libpq library.  For more clarity here is a small flow diagram:

Client Server Model:

Application -> libpq library (cs) -> TCP/IP network -> libpq (backend) ->
pgsql server

Merged Model:

Application -> libpq library (merged) -> pgsql server

One approach that we are having in mind is to use the SPI interface and
re-implement the libpq APIs.  Is there any other better approach?   Would it
be possible to implement the client server protocol into an API interface,
without involving the TCP/IP network?

Your thoughts and suggestions on this would be highly appreciated.

Rgds,
anna


-- 
'உண்மை ஒருநாள் வெளியாகும், \
அதில் உள்ளங்களெல்லாம் \
தெளிவாகும். பொறுமை ஒருநாள் \
புலியாகும், அதற்கு பொய்யும் \
                புரட்டும் பலியாகும்.'
                                     - பட்டுக்கோட்டை \
கல்யாணசுந்தரம் \
http://www.youtube.com/watch?v=0J71uLUvjnU&feature=related


[Attachment #3 (text/html)]

Hi All,<br><br>I would like to know about the best approach to take for providing a \
merged model of libpq library.  When I say &quot;merged model&quot; it means that the \
client and server would be running as a single process.  A single client libpq \
application can be linked to either the client-server libpq library or merged libpq \
library.  For more clarity here is a small flow diagram:  <br> <br>Client Server \
Model:<br><br>Application -&gt; libpq library (cs) -&gt; TCP/IP network -&gt; libpq \
(backend) -&gt; pgsql server<br><br>Merged Model:<br><br>Application -&gt; libpq \
library (merged) -&gt; pgsql server<br> <br>One approach that we are having in mind \
is to use the SPI interface and re-implement the libpq APIs.  Is there any other \
better approach?   Would it be possible to implement the client server protocol into \
an API interface, without involving the TCP/IP network?<br> <br>Your thoughts and \
suggestions on this would be highly appreciated.  <br><br>Rgds,<br>anna<br><br \
clear="all"><br>-- <br>&#39;உண்மை ஒருநாள் வெளியாகும், அதில் உள்ளங்களெல்லாம் \
தெளிவாகும். <br>பொறுமை  ஒருநாள் புலியாகும், அதற்கு பொய்யும் புரட்டும் பலியாகும்.&#39; \
<br>                                     -  பட்டுக்கோட்டை கல்யாணசுந்தரம் <br><a \
href="http://www.youtube.com/watch?v=0J71uLUvjnU&amp;feature=related" \
target="_blank">http://www.youtube.com/watch?v=0J71uLUvjnU&amp;feature=related</a><br><br><br>




[prev in list] [next in list] [prev in thread] [next in thread]