Arnulf,
You mention in this email thread that you are considering addressing
security.
We want to provide a secure mechanism for AJAX clients to access Web
Services and I'm interested to know if you have already, or are
intending to address this issue.
We have written the problem statement here:
http://tools.assembla.com/ajaxtrust
Arnulf Christl wrote:
Bob Basques wrote:
All,
The MOOSE project has been working with essentially the same
philosophy, with regards to normalizing the code into distinct
Chunks, which make the mixing and matching very easy. Integrating
services into it are very easy for example.
I think our coding style is very much aligned with other groups, more
actually than I thought a few weeks ago.
This is a very thought provoking conversation for me too. It's
getting me thinking about how to describe the MOOSE project a bit
better and describe it's strengths.
bobb
Hi Bobb,
just because it has not been mentioned yet, talking of diversity...
The project Mapbender is a managed web mapping application framework -
it is a server to create clients, think of a CMS for spatial data
services.
The scope of Mapbender is to manage hundreds of WMS layers and dozens
of WFS-t features. Many spatial data infrastructures in European
public administrations are managed (or "orchestrated" as OGC would
say) with Mapbender. This includes building a Capabilities cache, auto
update functionality for meta data, user and permission management,
toolbars, digitizing functionality and all kinds of things you need
for web mapping.
The long term goal of Mapbedner development is to include or connect
to other OSGeo projects like OpenLayers that will be the map "control"
of Mapbender. Through OGC interfaces there already is a lot of
meta-level interaction with MapServer, GeoServer, PostGIS - all at
different levels of involvement with OSGeo. Mapbender will probably
develop more in direction of security and management as that is
something we are still missing completely in the OSGeo stack and OGC
does not address it either (except from the limited DRM perspective).
I checked the demo link you sent around. If those maps were published
as a WMS service (maybe they are, have a link?) I could whip up a demo
site within minutes so that you can have a look around. I guess we
will be doing this kind of thing on a big scale at FOSS4G. Might be
interesting for you to find out where MOOSE would fit in to
potentially "fill a hole".
http://wiki.osgeo.org/index.php/FOSS4G2007_IntegrationShowcase
Best regards, Arnulf.
**************** You can't be late until you show up. ***************
************ You never learn anything by doing it right. ************
*** War doesn't determine who's right. War determines who's left. ***
>>> Schuyler Erle <[EMAIL PROTECTED]> wrote:
* On 1-Mar-2007 at 2:11AM PST, Cameron Shorter said:
>
> As Chris noted, Mapbuilder is in the process of merging OpenLayers
into
> its codebase. This involves throwing away a lot of our original code,
> but at the same time, makes Mapbuilder a more robust product
because we
> can focus on other areas.
And by that same token, we've tried very hard to make it possible to
separate out only the pieces of OpenLayers you want, and leave out the
parts you don't.
------------------------------------------------------------------------
_______________________________________________
Discuss mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/discuss
--
Cameron Shorter
Systems Architect, http://lisasoft.com.au
Tel: +61 (0)2 8570 5011
Mob: +61 (0)419 142 254
_______________________________________________
Discuss mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/discuss
