[OpenLayers-Dev] vector behavior
Christopher Schmidt
crschmidt at metacarta.com
Tue Apr 15 07:24:03 EDT 2008
On Tue, Apr 15, 2008 at 04:31:34AM -0600, Tim Schaub wrote:
> Hey-
>
> Christopher Schmidt wrote:
> > On Mon, Apr 14, 2008 at 10:02:13PM -0400, Christopher Schmidt wrote:
> >> On Mon, Apr 14, 2008 at 05:46:47PM -0600, Tim Schaub wrote:
> >>> Hey-
> >>>
> >>> Some may have already seen the proposal for new vector layer behavior.
> >>> http://trac.openlayers.org/wiki/Proposal/VectorBehavior
> >>>
> >>> This week, I'll be working on implementing a bit of this new design.
> >>> I'm focussed on an AtomPub protocol, an Atom format, and a somewhat
> >>> smartish BBOX strategy.
> >> Thanks for the email letting us know what's up.
> >>
> >> Out of curiosity: some Protocols seem likely to be 'trapped' within a
> >> single Format. I'm assuming that you don't see any problem with that, so
> >> long as it is sufficiently documented. I'm asking only because the
> >> majority of protocols seem to clearly be in a position where they'll be
> >> able to cope with many formats -- WFS read support, AtomPub support,
> >> etc. -- while a minority -- ESRI-REST, WFS-T/write, etc. -- are tied to
> >> a specific Format. Does this make sense? Is a format-specific protocol
> >> still a protocol? (I think yes.)
> >
> > Alright, based on my assumption, I've gone ahead and implemented Google
> > Gears and HTML5 Local Storage support.
> > http://crschmidt.net/mapping/localdb/ . Patch is at
> > http://crschmidt.net/~crschmidt/localdb.patch ; it's in SVK. When you
> > guys are done on your push, let me know, and we can talk about the best
> > way to integrate.
> >
>
> Looks nice. I really want to make sure we get this right before being
> stuck with any one design. The more implementations the better - as
> long as nobody is promising *anybody* about things being set in stone.
>
> Perhaps SQL is a better protocol name (just a bit closer to "protocol"
> than HTML5).
Yeah; I realized that after I wrote it :) Then we'd have various
implemenetations: SQL.HTML5/SQL.GoogleGears, maybe? I dunno. There's
definitely a lot of cleanup in this regard: I'm happy to continue
discussing it once you're past your near-term deadline :)
For now, I think it makes a cool demo regardless.
Regards,
--
Christopher Schmidt
MetaCarta
More information about the Dev
mailing list