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

List:       postgresql-general
Subject:    Re: [HACKERS] [proposal] protocol extension to support loadable stream filters
From:       Brent Verner <brent () rcfile ! org>
Date:       2005-04-29 0:49:28
Message-ID: 20050429004928.GA9390 () rcfile ! org
[Download RAW message or body]

[2005-04-28 10:00] Tom Lane said:
| Brent Verner <brent@rcfile.org> writes:
| >   Would it be sane to recognize a specific PG_PROTOCOL_MAJOR
| > to enter the filter-negotiation process?  PG_PROTOCOL_MINOR
| > would then be used to lookup and call a ptr to the filter's 
| > create() in CreateStreamFilter...
| 
| Looks reasonable enough to me ...

  Now, the hard part...where should this code live?  I'm thinking a 
src/transport directory seems sensible.

  StreamFilter.[ch] will contain the base StreamFilter along with 
various utility functions.  StreamFilter implementations will reside
in their own subdir.

  src/include/transport/StreamFilter.h
  src/transport/StreamFilter.c
  src/transport/zlib/...
  src/transport/ssl/...

Comments/ideas appreciated.

cheers.
	b


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match
[prev in list] [next in list] [prev in thread] [next in thread]