We've ingesting larger and larger files into our Fedora and we want them stored in Fedora managed streams. This means that the ingest operation must copy the data to a new location. Sometimes we pair the ingest call with use of the upload service, but more often we're copying gigabyte files from a third place to Fedora, someplace like iRODS or a locally mounted drive.
My concern is that we've had to increase the timeouts on our apache server in order to keep it from "hanging up on" the ingest client with a 503. Long timeouts are generally considered a bad idea and leave you vulnerable to denial of service style attacks. Currently the SOAP ingest call waits until ingest completes, with all copying, before returning success. Are there are ideas for how we can avoid these long connection times? Some kind of polling? Maybe we should have our client respond to the occasional 503 by polling until the new PID shows up in the repo? any advice appreciated, Greg -- ___ Gregory N. Jansen Developer - Carolina Digital Repository UNC Chapel Hill Libraries ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
