Ok, hopefully this is quick and I just missed something. I am building a click-edit Google map, and everything is alive and functions except for 1 element -- saving marker data. The difficulty (as I see it) is a choice between two ways of moving marker data.
Layout:
Map table -- has/stores map specific settings, center, zoom, etc
Marker table -- has/stores marker data and is keyed to a map entry based on $mapid
The ability to reuse markers without having to re-enter them is an unexpected benefit of this design.
Methods:
1. XMLRPC all the way. I click a point to create a marker, I edit that marker inline in the javascript, and I can save it directly vi XMLRPC. Piece of cake. Not much code, not much effort. The problem is going to be one of access. I can write XMLRPC code to dump all markers, or even in a worst case scenario, the problem of map or location based spam becomes a nightmare. The only token that I am aware I have access to would be document.cookies.PHPSESSID, but I don't know how that relates back to anything in Drupal that would let me authenticate and verify a content creator. The second problem with an XMLRPC only method is the fact that any new markers will/can get updated in a marker table before the map node has a nid assigned (or even exists for that matter)! The work around for that would be a staging table where orphans get deleted after a specified age limit, everything is keyed on PHPSESSID, and markers that belong to a map node that actually gets created get migrated to the live marker table when the submit occurs. Gut feeling tells me this is the method I should be trying to use, but I really don't have much of a starting point as far as Drupal and user verification are concerned.