You're correct that App Engine's filesystem is not writable. This is not likely to change soon, so any libraries that you depend on which assume a writable file system will have to be updated to use a supported mechanism. As you can see from the following wiki page, a growing number of libraries and frameworks are compatible with App Engine, Hibernate notwithstanding. http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine
Regarding your third point, App Engine does include a URL Fetch service which should allow you to issue HTTP requests (including POSTs) to other websites running on ports 80 or 443. In addition to the low-level API, a java.net-based wrapper is available: http://code.google.com/appengine/docs/java/urlfetch/ - Jason On Sat, Aug 29, 2009 at 4:15 AM, sandeep <sandeep.mal...@gmail.com> wrote: > > Google app engine is good but it has limitations like: > 1. You cant create temporary files. Most java libraries rely on a > temporary folder for scratchpad. As GAE doesnt support filesystem > operations, all these go for a toss? > > You cant upload files on to a file system. How does one expect to > manage static content then? > > Any plans for temp files support atleast?? > > 2. Also had GAE supported hibernate it would have been a super boost > as most apps run today with spring + hibernate. > > 3. Also you cant crawl other websites as http port is blocked that > means you can't do anything like HTTP post?. > > > Any suggestions on these esp point 1 ?Please help. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
