Interesting question; usually people split geoserver into separate machines in
order to load balance. A lot of time has spent getting GeoServer close
physically to the data in order to be efficient; there is no distribution
between the data reading library and the GeoServer code using it to handle web
feature server request. Literally as each feature is read out of the database
the xml is being generated.
If you had to (say for a security setup?) is set up cascading wms in order to
have a front end geoserver talk to a backend geoserver that actually draws the
pictures.
--
Jody Garnett
On Tuesday, 15 February 2011 at 10:00 PM, Ankers, David wrote:
> Hi all,
> Due to the physical architecture in which I need to deploy GeoServer, I was
> wondering if anyone had experience of splitting GeoServer across servers.
> As an example, I would deploy the Internet aware parts (say the WFS and WMF
> services) on one server, and the data aware services (i.e. connect to Oracle)
> on another.
> If anyone has any info, I’d b grateful!
> Thanks,
> Dave Ankers
> ESG Architecture
> Information Systems
> Land Registry
> Seaton Court, Plymouth
> x: 64635
> t: 0300 0064635
> e: [email protected]
>
> Land Registry's House Price Index is now live. www.landregistry.gov.uk
>
>
> If you have received this e-mail and it was not intended for you, please let
> us know, and then delete it. Please treat our communications in confidence,
> as you would expect us to treat yours. Land Registry checks all mail and
> attachments for known viruses, however, you are advised that you open any
> attachments at your own risk.
>
>
>
> The original of this email was scanned for viruses by the Government Secure
> Intranet virus scanning service supplied by Cable&Wireless Worldwide in
> partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On
> leaving the GSi this email was certified virus free.
> Communications via the GSi may be automatically logged, monitored and/or
> recorded for legal purposes.
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
