Thanks, for all the comments. much appreciated. When the request for php was made, I didn't really understand it myself. But I think it was because everybody in the office isn't very technical and when I leave (I am a student worker) they arn't sure how to maintain the map. So I think what they were going to after is have me make a "admin section" to build the data entries.
Ill check out the polygon encoding. Again, thanks. On Oct 16, 3:53 am, "warden [Andrew Leach - Maps API Guru]" <[EMAIL PROTECTED]> wrote: > On Oct 16, 6:44 am, daniel <[EMAIL PROTECTED]> wrote: > > > I currently have a map pulling data from an xml file. It works fine > > for what my purposes, but when it goes into production, it will be > > used by 10k users (at least) simultaneously. > > All that means is that 10000 people will have visited your web page > and downloaded it and the xml file. There's no more interaction than > that, by the look of it. Do you really mean that there will be 10k > **simultaneous** users? How do you calculate that? Bear in mind that > once the server has satisfied one request it can move on to the next > one. Your users may be viewing the map at the same time, but each > request is separate. > > Even if all 10000 hit your server simultaneously, it's down to the > server to manage those requests. I reckon it's extremely unlikely that > for a campus map you'll get anything like that instantaneous load. > > > I have recently read alot of people are making the move to php with > > google maps, but I really can't seem to understand why. Maybe to have > > thousands of data points? Or does it greatly improve speed and > > reliability for the users? > > PHP is a server language which makes integration with a server side > database (especially MySQL) easy. The reason you've found a lot of > people using PHP is so that they can get a tailored subset of data for > each map user -- eg to search for POIs near a user-specified location. > > If you have a small dataset, there may not be a great deal of point. > Your XML file is small, so in this case you could justifiably transfer > the work to the client. > > > here is a link to my map just in case you would like to see what it > > looks like currently.http://dajohnson1s.dvrdns.org > > > Oh, I plan to add driving directions, move the sidebar to populate > > under each checkbox respectively. And I am currently in the process > > of adding polygons to give the impression of the buildings (about 30 > > buildings). Not sure if those are relevant, but just in case. > > Thirty polygons shouldn't be *too* bad: if you're dowloading complex > shapes though you might consider encoded polygons to reduce the > download time. Driving directions are requested and drawn client-side; > there's likely to be no interaction with your server. > > As you appear to have a static dataset (albeit with category > selection) it doesn't appear to me that investment in a server-side > database and processing is hugely worthwhile. If you end up doing more > with your map you may need it in the future. > > Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
