to greg, thank you for your insight on the matter. it's not that i want to force using a utility class, its just that, well, its a requirement for me (to use a utility class, since other fellow devs here in my team will use it) and i thought its more convenient. and on the matter of where to place the fetch calls, i made it that way with "create things only on the time that you would need them". but i guess that the lesson learned here (for me) is "flexibility".
to jason, thank you for your technical explanation of these callback objects. ill experiment with them a bit more when i have time. unfortunately, my team decided to implement a singleton on the server- side to parse, then transfer the data onto beans, which will then be accessed by services. but this has been a great learning experience for me, thanks to all those that replied. mives29 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
