Vitali Lovich schrieb: > > Android: > - The browser coming with G1 is not able to do > HTTP Basic Authentication (WTF?) > > That seems strange & unlikely given that it's Chrome (or at least some > kind of Webkit-based browser). Try running your app in Chrome on the > desktop - does that work? Do you have the latest updates on the phone?
I don't have Chrome on the desktop (I don't agree with the terms of usage, so I'm not able to install it). The phone was updated about one month ago. The phone's message is quite clear: "Das Authentifizierungsschema fuer die Site wird nicht unterstuetzt." (The site's authentication-scheme is not supported) The server's response-header looks OK to me: $ telnet 127.0.0.1 9000 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. GET / HTTP/1.0 Host: localhost HTTP/1.1 401 Unauthorized Date: Wed, 08 Apr 2009 13:44:31 GMT Server: IS/5.7.20_14442 WWW-Authenticate: basic realm="HUB Admin Realm" Content-Type: text/html Content-Length: 1127 Connection: close > Mobile Safari: > - Safari on an iPod touch 2G is showing the application after > some while and crashes after doing some RPC-calls. > - Safari on an iPhone 2G shows the application but instead > of crashing, the browser fails to do RPC-calls after a while. > > Do you see these problems on the desktop version of Safari? No, the application is running smoothly there. > The iPhone > & desktop versions are pretty much identical in the backend. What do > you mean by crashes? When working with the application it suddenly vanishes in the same way it do when you press the "Main"-button. I never saw this behavior on other pages, so I assume that it's killed by the operating system because there is not enough memory and Safari wasn't able to free up enough ressources after being told so by the system (which lead to the kill of the application). So "crashing" might not be the correct term here but the user- experience is the same ;-) [Splitting GWT-application to reduce memory-consumption] > Build from trunk & use GWT.runAsync > <http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting>. Looks good (meaning that I still can skip 1.5 and can go from 1.4.60 to 1.6 directly). Two questions that I don't find answered in the page you linked: 1. My application is already modularized, every page allowing the administration of one particular "service" is a class derived from a superclass "AbstractServicePanel". When clicking on an entry in the list of services, a method is called that is evaluating the panel to be initialized: AbstractServicePanel panel = null; try{ if (status.handlingName.equals("AS2Service")){ panel = new As2ServicePanel(); } else if (status.handlingName.equals("LogService")){ panel = new LogServicePanel(); } else if (status.handlingName.equals("authplain")){ panel = new AuthServicePanel(); } else if (status.handlingName.equals("commlogplain")){ panel = new CommunicationLogServicePanel(); } [etc] else if (status.handlingName.equals("AdminService")){ panel = new AdminServicePanel(); } } catch(Throwable t){ callback.onFailure(t); return; } if (panel == null){ panel = new UnimplementedPanel(status); } callback.onSuccess(panel); The callback removes a previously shown panel and adds the new one. Is it enough to put the whole if-cascade into one GWT.runAsync or do I have to do it for every if-statement if I want to let GWT perform a deferred loading for each panel? 2. Is it possible to "unload" loaded parts? Otherwise I might be able to run the application in the beginning but the longer the application is used (i.e. the more panels are loaded and initialized), the higher the likelyhood of running out of ressources will be. > You may also want to ensure > that you aren't leaving cycles in your references, thereby preventing > garbage collection (i.e. when you remove a widget, remove it's listeners > as well). Is there a link to the GWT-documentation where this problem is explained further? If I have a Panel, containing a button and I add a ClickListener to that Button, do I really have to remove that ClickListenner from the Button before removing the Panel? > Since you're also dealing with the mobile space, you may want > to make sure that when you hide a composite, you actually remove it from > the page & then recreate it as necessary if it gets added back (unless > it's really expensive). I've got quite complex Dialog-boxes. How can I remove a Dialog-box? At the moment I'm only calling hide(). Thanks and regards, Lothar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
