Thursday, May 07, 2009

Magnum Opus

I recently (well, two months ago) and wrote down a great deal of thoughts about the architecture for web mapping we are pushing at OpenGeo, and it's up on the website now.

http://opengeo.org/publications/opengeo-architecture/
 

6 comments:

Ian Turton said...

What license did you use for this document? i.e. can I cut and paste bits into my course?

sgillies said...

HTTP == transport ... sigh.

Paul Ramsey said...

What's the correct terminology, oh best beloved web pedant?

Paul Ramsey said...

@Ian, should be updated online soon, but CC-SA.

jlhgis said...

Nice! Thank you very much for sharing.

This appeared at just the right time - when I seem to be the lone proponent of using open standards, open source, mix and match software stacks, etc. (basically anything outside of a monolithic, proprietary, commercial stack from the 900 lb GIS gorilla) on a State GIS Architecture Working Group. I feel like I have a little red dot persistently aimed at my forehead (and at least one or two on my back). This will be quite helpful.

sgillies said...

I'll list some of the good stuff you'll miss when you use HTTP as transport only (perhaps by tunneling all sorts of methods through POST):

- Safety of GET vs POST
- Ability to modify resources with PUT/DELETE
- Caching using HTTP's built-in expiration and validation
- Content negotiation (for better or worse)

Your GeoWebCache, for example: you only need such a thing because GeoServer considers HTTP to be only transport when doing its WxS thing. You could use something more generic from the open web stack like Varnish if your app server was taking full advantage of HTTP.

About Me

My Photo
Victoria, British Columbia, Canada

Followers

Blog Archive

Labels

bc (37) it (29) postgis (20) icm (11) video (11) enterprise IT (10) sprint (9) open source (8) osgeo (8) cio (6) foippa (6) gis (6) management (6) spatial it (6) enterprise (5) foi (5) foss4g (5) mapserver (4) outsourcing (4) politics (4) bcesis (3) oracle (3) COTS (2) architecture (2) boundless (2) esri (2) idm (2) natural resources (2) ogc (2) open data (2) opengeo (2) openstudent (2) postgresql (2) rant (2) technology (2) vendor (2) web (2) 1.4.0 (1) HR (1) access to information (1) accounting (1) agile (1) aspen (1) benchmark (1) buffer (1) build vs buy (1) business (1) business process (1) c (1) cathedral (1) cloud (1) code (1) common sense (1) consulting (1) contracting (1) core review (1) crm (1) crockofshit (1) cunit (1) custom (1) data warehouse (1) deloitte (1) design (1) development (1) digital (1) email (1) environment (1) essentials (1) evil (1) exadata (1) fcuk (1) fgdb (1) fme (1) foocamp (1) foss4g2007 (1) ftp (1) gds (1) geocortex (1) geometry (1) geoserver (1) google (1) google earth (1) government (1) grass (1) hp (1) iaas (1) icio (1) industry (1) innovation (1) integrated case management (1) introversion (1) iso (1) isss (1) isvalid (1) javascript (1) jts (1) lawyers (1) mapping (1) mcfd (1) microsoft (1) mysql (1) new it (1) nosql (1) opengis (1) openlayers (1) oss (1) paas (1) pirates (1) policy (1) portal (1) proprietary software (1) qgis (1) rdbms (1) recursion (1) redistribution (1) regression (1) rfc (1) right to information (1) saas (1) salesforce (1) sardonic (1) seibel (1) sermon (1) siebel (1) snark (1) spatial (1) standards (1) svr (1) taxi (1) tempest (1) texas (1) tired (1) transit (1) twitter (1) uber (1) udig (1) uk (1) uk gds (1) verbal culture (1) victoria (1) waterfall (1) wfs (1) where (1) with recursive (1) wkb (1)