The original message was received at 2010-01-13 07:16:02 -0800 from postoffice.(null) [10.0.0.1]
----- The following addresses had permanent fatal errors ----- <[email protected]> -----Transcript of session follows ----- ... while talking to postoffice.(null).: >>> RCPT To:<[email protected]> <<< 550 5.1.1 unknown or illegal alias: [email protected] 550 <[email protected]>... User unknown
-- 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.
Reporting-MTA: dns; postoffice.(null) Received-From-MTA: DNS; postoffice.(null) Arrival-Date: 2010-01-13 07:16:02 -0800 Final-Recipient: RFC822; [email protected] Action: failed Status: 5.1.1 Remote-MTA: DNS; postoffice.(null) Diagnostic-Code: SMTP;550 5.1.1 unknown or illegal alias: [email protected] Last-Attempt-Date: 2010-01-13 07:16:02 -0800
--- Begin Message ---============================================================================= Today's Topic Summary ============================================================================= - Local call to a service instead RPC [1 update] http://groups.google.com/group/google-web-toolkit/t/5c1b7f8ea74c6dfe - simple question (offtopic?) [1 update] http://groups.google.com/group/google-web-toolkit/t/6621f55635cbd78 - Force image caching in gallery [1 update] http://groups.google.com/group/google-web-toolkit/t/df478968a49bf0dc - General question about project architecture. [1 update] http://groups.google.com/group/google-web-toolkit/t/c2774cb5c9b8851e - RunAsyncCallback [1 update] http://groups.google.com/group/google-web-toolkit/t/783cac72e23950d1 ============================================================================= Topic: Local call to a service instead RPC Url: http://groups.google.com/group/google-web-toolkit/t/5c1b7f8ea74c6dfe ============================================================================= ------------------------- 1 of 1 ------------------------- From: Sripathi Krishnan <[email protected]> Date: Nov 14 05:58PM +0530 Url: http://groups.google.com/group/google-web-toolkit/msg/7fbfe92ebe2fc495 > My all application is running in the same JVM > I think you have the wrong idea about GWT. GWT eventually compiles client side code into javascript. The Service call is something that the javascript code executing in browser makes to your server side code which is written in java. Hence, the concept of a Local Interface doesn't make sense at all. --Sri 2009/11/13 Badawi <[email protected]> ============================================================================= Topic: simple question (offtopic?) Url: http://groups.google.com/group/google-web-toolkit/t/6621f55635cbd78 ============================================================================= ------------------------- 1 of 1 ------------------------- From: Sripathi Krishnan <[email protected]> Date: Nov 14 05:35PM +0530 Url: http://groups.google.com/group/google-web-toolkit/msg/50ee7dba44037909 GWT is just plain old javascript at the end of the day. Since it is not possible to achieve this use case in javascript, you can't do it in GWT. Google Gears (a browser extension) provides a way to drag and drop files and upload them to the server. I haven't tried it myself, but this article<http://www.appelsiini.net/2009/10/drag-and-drop-file-upload-with-google-gears>explains the concept. --Sri 2009/11/11 K. <[email protected]> ============================================================================= Topic: Force image caching in gallery Url: http://groups.google.com/group/google-web-toolkit/t/df478968a49bf0dc ============================================================================= ------------------------- 1 of 1 ------------------------- From: Sripathi Krishnan <[email protected]> Date: Nov 14 05:30PM +0530 Url: http://groups.google.com/group/google-web-toolkit/msg/ebeb465820f5ead0 Are the images dynamic (user can upload them), or static (known at compile time)? If the images are from a fixed set of images that are available at compile time, you should consider using ImageBundle<http://code.google.com/p/google-web-toolkit/wiki/ImageBundleDesign>. It would take care of most of your concerns. In addition, it can bundle multiple images in a single file, saving further http round trips. If you are images are dynamic, or if you are not using GWT 2.0, you will have to set appropriate HTTP Cache headers when the image is served. Essentially, your server tells the browser "This image is not going to change for the next few years, so you can cache it till then without bothering to ask me if it has changed". A typical strategy is assigning every image a unique name based on a MD5 hash of its contents. You then set a far in the future expiry date on that image, so that browser doesn't go back to the server to see if it has changed. If the image changes, you will generate a totally different file name, and hence the browser will download it again. --Sri 2009/11/11 dicko <[email protected]> ============================================================================= Topic: General question about project architecture. Url: http://groups.google.com/group/google-web-toolkit/t/c2774cb5c9b8851e ============================================================================= ------------------------- 1 of 1 ------------------------- From: Sripathi Krishnan <[email protected]> Date: Nov 14 05:20PM +0530 Url: http://groups.google.com/group/google-web-toolkit/msg/2663064e5d1d0e3f Multiple modules is the wrong way to use GWT. GWT highly recommends using a single module. Most of the performance optimizations GWT does relies on the fact that you have a single, monolithic module. Plus, as you observed, the time to build your application keeps growing as you add more modules, so it doesn't scale well. Part of the problem is deciding whether you are building a "Web App" or a "Web Site". Lots of discussions<http://www.clyral.com/za/pages/web/website_vs_webapplication.html>can be found on this topic. GWT is great if you want to build a Web App. Typically, there is only a single HTML page, and different "screens" are manipulated on the client side using DOM. But if you are building a traditional, multi-page Web Site (nothing wrong with that), then GWT is not for you. You are better off using one of the many javascript libraries. So, lets assume you decide you want to build a web-app, and want to use GWT to do so. To get started, stick to a single HTML page with a single GWT Module/Entry Point. Adding multiple "screens" is adding a new FlowPanel or Composite with your content. Or perhaps, you have all "screens" built into the original HTML page, and you just hide/unhide the divs based on user action. The above approach works well if you have a few (say less than 10) screens. If your application grows bigger and more complex, you would want to start following some established patterns. The MVP pattern has been touted as the "way to build web-apps". Just do a google search, there are a lot of articles on that subject. Also, catch Ray Ryan's talk on GWT Architecture and best practices<http://code.google.com/events/io/2009/sessions/GoogleWebToolkitBestPractices.html>. --Sri 2009/11/13 David C. Hicks <[email protected]> ============================================================================= Topic: RunAsyncCallback Url: http://groups.google.com/group/google-web-toolkit/t/783cac72e23950d1 ============================================================================= ------------------------- 1 of 1 ------------------------- From: Sri <[email protected]> Date: Nov 14 02:28AM -0800 Url: http://groups.google.com/group/google-web-toolkit/msg/a72f948967919f89 Just in case someone reads through this issue later - there is an interesting discussion on using GIN with runAsync() over here - http://code.google.com/p/google-gin/issues/detail?id=61 On Oct 30, 8:34 pm, Sripathi Krishnan <[email protected]> wrote: -- 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=.
--- End Message ---
