I'll throw in here.... GWT is primarily a client side technology, so in your statement "better off sticking with PHP, JS, & CSS", GWT would replace only the last 2. PHP (obviously) only runs on the server. By choosing GWT you will still need to choose a server side technology assuming you want to connect to a database. Many people are familiar with PHP, so they stick with that, communicating between client and server using JSON, which GWT handles terrifically. You can also use Java for your server side technology, and then you can very simply use GWT-RPC to handle your communication. As for connecting to MySQL, Java will connect to MySQL all day long, as will PHP. Just a matter of what syntax/stack you are familiar with. The key thing to focus on here with GWT is that it is an AJAX client "library" that makes it very easy to build powerful AJAX web clients (or substitute your favorite acronym for that) using Java syntax. If you use Java for your server tier, then you get to use a teenie bit more GWT, but that's it.
Does that make sense? Later, Shaffer On Sep 2, 6:54 pm, David Given <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > spierce7 wrote: > > [...] > > > By the way, I'm going to need to integrate with a web database. The > > obvious one for me was MySQL, but that was mainly because PHP > > integrates so easily with it. What kind of options do I have with this > > while using GWT? I'd rather not have to have GWT integrate with PHP, > > and then MySQL, or some other ridiculous thing. What options do I have > > here? Thanks in advance! > > I'm using Berkeley DB JE for one of my apps; it's a pure-Java > reimplementation of the old classic Berkeley DB non-relational database. > It's got some really nice Java reflection glue that combines well with > GWT's RPC glue. I can pull an object out of the database on the server > and pass it directly to the client in about three lines of code, and GWT > and Berkeley DB take care of all the plumbing. And because it's pure > Java, there's no extra dependencies on the server --- you just drop the > jarfile in WEB-INF/lib and it Just Works(tm). > > A server-side RPC implementation can be as literally trivial as this: > > DataObject getFromDB(int key) > { > try > { > return _index.get(key); > } > catch (DatabaseException e) > { > return null; > } > > } > > - -- > ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─────http://www.cowlark.com───── > │ > │ "People who think they know everything really annoy those of us who > │ know we don't." --- Bjarne Stroustrup > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ > > iD8DBQFKnxPQf9E0noFvlzgRAhmbAJ9VSY0eSfTjCoUUwNyJtf32UyYNcgCghhbe > Qe2VV/Tvae3wndsEBQJvyKo= > =4rPN > -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
