Direkt zum Hauptbereich

Welcome People of People

You can take it out here. If you're nice, I shall come back to you.

Kommentare

Catherin hat gesagt…
Ay, que chevere tu pagina. Y tu quien eres?
Anonymous hat gesagt…
mmm... long time since!
Anonymous hat gesagt…
I see you are working on your page again... is it that time of the year already or just a midlife crisis thingy?

Wish you all the best and keep it up!

Cami
Anonymous hat gesagt…
hey DUH-UH!
Anonymous hat gesagt…
schöne Bilder!
Anonymous hat gesagt…
That is old stuff. Have you any new things?
Anonymous hat gesagt…
who the hell listens to anime music?
tulio camminati hat gesagt…
!
I think this kind of music comes too short. It is actually pretty good.. check it out.
Anonymous hat gesagt…
Yeh yeh.. mother f***!
Anonymous hat gesagt…
i like the new pictures in your gallery.
Claudia hat gesagt…
mmm.. nothing new on your site?

Beliebte Posts aus diesem Blog

Python and Access-Control-Allow-Origin

Ok, here is something that probably happens a lot: You are trying to do some .js (if not you should get started), and write some code in your favorite ide, save it, load it in your favorite browser and everything is ok. You are a good developer and start making packages and loading your files when you need them: lazy . You don't want to overdo things, and manage to put stuff into a bunch of .js and .html. You load them into your browser and BAM: Access-Control-Allow-Origin   Failed to load resource: Resource failed to load   So now you are all WTF, right? You Google (some would Bing ) it and sure enough, what you were thinking is the ugly true and by now you get angry as a bird. Why? Ok, for those that didn't know there is a thing called Same Origin Policy , that forbids you from loading stuff across different domains and bla bla bla... So what does it has to do we you? You sure enough are not trying do load across domains, your are loading a file... you may think, but no...

ThreadLocal as an Enum - I'm not afraid to admit it!

Well, as disturbing as it might be, I am not afraid to at least admit it: I did not know about the elegance of the following construct: public enum TLData { INSTANCE; private final ThreadLocal< String > myData = new ThreadLocal< String >(); public String getMyData() { return myData.get(); } public void setMyData( final String myData) { this .myData.set(myData); } } Since you are using an Enum, nobody can create new members from outside, you don't have to care about privatizing any methods and you can access it as easy as: public class myClass { public void myMethod() { /** * setting the data */ TLData.INSTANCE.setMyData( "some data" ); /** * getting the data */ String myData = TLData.INSTANCE.getMyData(); } } Isn't that fancy? I had to admit I never thought of it myself. A colleague of mine had to put it under my nose.