Skip to main content

Render images by java code or read images from a static path?



Here's my code:





1.Java Code:







public static void getImg(Long itemId) {

try {

Item item = Item.findById(itemId);

if (item.img != null && item.img.getFile() != null{

response.setContentTypeIfNotSet(item.img.type());

renderBinary(item.img.get());

}

} catch (Exception e) {

Logger.error("Can't find image,itemId = " + itemId);

}

}



html : < img src="@{{ Items.getImage(123)}}"/>







2.







html : < img src="/public/images/123.jpg"/>







I'm using playframework and the samples from documentation display images via the first version. What's the different (deep into mechanism) between them, especially in response performance ?


Comments

  1. In the 1st version, since you get the actual filename from some business logic (and/or database), you can easily rename/replace the image of id '123' without needing to change the presentation tiers.

    If the image of id '123' is in a protected folder (HTTP Basic Authentication or similar), your business logic could make sure the access is granted through an application wide security mechanism.

    You could also have versioning of the image, by providing the path of the desired version according to other Request/Session parameter and logic.

    In the 2nd case, it is possible to perform the above scenario but much more costly in development time and possibly configuration.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex