> I guess I hadn't fully grasped the way the client's browser interacts > with an XML file...
The point is that is doesn't interact at all, it can only read it. > ... I wonder if I can use a > similar procedure to access the XML file and write the browser's image > of the XML file back to the original ... Nope. You could write javascript to build up a great big string that looks like XML, send that using POST to some server code which you've written to expect it, accept it and make a real XML file out of it. It wouldn't be smart - any user can totally trash your XML file in a twinkle. This might feel obstructive, it is supposed to be. Servers do not allow people to arbritrily manipulate their files. Browsers do not allow other people's webpages to manipulate their client files. There will be much less pain and traffic across the net, if you adopt a conventional approach. User clicks 'delete', a short message is sent to the server identifying what needs to be done to whom, code at the server checks that is allowed and carries out an action - in this case, deleting a single identified item from its file. Probably followed up with an 'OK' message for the user, or maybe refreshing the whole map with the updated data in this case. cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
