Announcing GWTUpload

[Manuel Carrasco]

I'm pleased to announce GWTUpload.

GWTUpload is a library for uploading files to web servers, showing a progress bar with real information about the process (file size, bytes transferred, etc). It uses AJAX requests to ask the web server for the upload progress. It has two components written in java, the server side with servlet and utility classes, and the gwt client side.

JsUpload is the client library but compiled and exported into javascript, so users that don't develop in java can use it directly in web pages. It provides a server program written in perl which can be installed in any web server as a cgi-bin script.

Thanks

Manolo Carrasco Moñino

[Kwhit]

Great stuff - I'll be using that very soon. Any chance of a cancel
button to cancel an ongoing upload?

[Jan Ehrhardt]

Are there any plans to support commet in the library? It would allow me to have fewer Ajax Requests to get the curren state of the upload.

Jan

[Max]

Quick question: Does it supports cross domain uploading?

Here is what I mean. Let's say I have application hosted on google
appengine and I would like to upload 500mb file to another server from
my GWT app on GAE to my own server that is on different domain/ip. Am
i going to be able to get responses back from the server?

Thanks

On Jul 17, 12:22 am, Manuel Carrasco <manuel.carrasc...@gmail.com>
wrote:

> I'm pleased to announce GWTUpload.
>

> GWTUpload <http://code.google.com/p/gwtupload/> is a library for uploading

[Manuel Carrasco]

It is rather difficult to cancel the upload process. Although  it is possible to notify the server to cancel the request but I'm not sure if it is possible to easily close the socket from the server in order to make the client cancel the upload. I'll play with this feature.

On Fri, Jul 17, 2009 at 3:04 PM, Kwhit <kwhitt...@gmail.com> wrote:

[Manuel Carrasco]

So far I've no plans to support commet, but it could be a possibility in the future.

[Manuel Carrasco]

No it doesn't support cross domain. It uses ajax so the status servlet has to be in same server of the application.

I see two  possible implementations for this feature: the upload server communicating the progress to your server,  or using cross-site scripting with callback functions.