On Fri, Feb 15, 2008, Amos Jeffries wrote: > I'd choose (3). Some of the basic types have clean headers already. > Is it possible to incrementally grow eCAP access to the internals of > squid? Starting with, ie just a buffer of page text, and work the API up? > I mean, we publish the available cleaned squid .h for its use starting at > lowest levels needed to support eCAP and working the way up to full > control paths. So the eCAP library never defines its own seperate types > publicly, but uses the squid ones as they get cleaned up. > > I imagine the basic first-signup users of eCAP will be wanting to perform > content-filters on pages as they arrive. That only needs a read-only > buffer of the page data and a hook to allow/deny the transaction.
If you don't tidy up stuff early on then you end up introducing more dependencies which will make restructuring more of a pain. Adrian -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
