I have a DynamicWebResource which is going to pull data out of a database. Some of the downloads will end up being quite large (possibly a couple of hundred MB).
I have successfully implemented the functionality using DynamicWebResource and extending ResourceState to provided the correct byte array. My concern is that this method will not scale, as it involves loading the entire download byte array into memory. Is there a way to do this more efficiently? Looking at DynamicWebResource, it looks like perhaps I could just override IResourceStream getResourceStream() instead of the getResourceState() method. Any problems/gotchas doing that? Is there a more standard/"wicket" way of doing it that I should be aware of? Thanks! -- View this message in context: http://www.nabble.com/Efficient-DynamicResource-Handling-tf4088361.html#a11620660 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
