On Jun 17, 6:52 am, Eric <[email protected]> wrote:
> Ross,
>
> Sounds great, I appreciate the guidance. Is there any code off the top
> of your head that you share to get me started with this conventional
> approach? Or anywhere you could direct me where someone has written
> something similar? This must be a common thing to do.
Very common. Many ways to do it. The question boils down to: how to
save data from a web client to the server hosting the page.
The work of saving the data is mostly done on the server, using data
and perhaps instructions sent to it from the client (the user's web
browser).
Your starting point might be to find out what you can do on your
server.
This has nothing to do with the Maps API or even Javascript, which is
99% used only in the client. So the following is offered with the
expectation that you may have to journey off on a path of learning
about web page-database transactions, before coming back here with
mapping questions :-) .
Many commercial ISPs/web hosts provide server databases to the sites
they host; these days it's common to see that offered in the form of a
PHP/MySQL package. PHP scripts catch the data submitted from the web
page, and hand it to MySQL to store it. PHP can also generate XML from
a MySQL database, giving you a way to generate a new XML file for your
map. More dynamically, your page could employ PHP to get the data from
the MySQL db and had it directly to the mapping script in your page --
no permanent XML file needed. (But leave that off for now until you
get the *saving* part down.)
PHP/MySQL is just one of many approaches -- I most enjoy working in
Perl. If desperate, one could use a simple "Guest Book" script
provided off the shelf by many ISPs for storing and serving up map
data...
>From the file paths you posted, it looks like you're on a university
site, so you'll need to check with the administrators about what
database and scripting capabilities they provide you.
When saving user-altered data to a web server, you face a multitude of
concerns over security, data integrity, access permissions, and
malicious user actions. All the more reason to start out with some
sort of package from your web host; you wouldn't want to start from
scratch on any of these concerns.
HTH
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
