Comments for The .Net frog

Comment on Yet another blogger on earth! by Catering

Catering — Sun, 18 Jul 2010 12:45:27 +0000

Caterers (????????)and their staff are part of the food service industry. When most people refer to a “caterer”, they are referring to an event caterer who serves food with waiting staff at dining tables or sets up a self-serve buffet.
The food may be prepared on site, i.e., made completely at the event, or the caterer may choose to bring prepared food and put the finishing touches on once it arrives. The event caterer staff are not responsible for preparing the food but often help set up the dining area. This service is typically provided at banquets, conventions, and weddings. Any event where all who attend are provided with food and drinks or sometimes only hors d’oeuvres is often called a catered event.

Comment on Yet another blogger on earth! by ????????

???????? — Sun, 18 Jul 2010 12:44:05 +0000

????? ????? ?????????? ?????? ???? ??? ????? ????? ??????? ?? ??? ?”??????”. ?????? ?????? “?’?????” – ??? ?? ??????? ?????? ???? ?”?’??????” – ??????? ????, “??????’?, “?’???’?????, “???’??” ??????? ??????? ?????, ??????? ????????? – ????? ?????? ?? ???.
?? ?????? ??? ???????? ??????????, ???? ???? ?????? ?????? ??????, ?????? ??????? ??? ????????. ?????? ?????? ?????? ?? ???, ??? ????? ???? ????? ???, ??????? ?????? ?? ???? ????? ???? ?? “???????” ????? ?? ?????.

Comment on Yet another blogger on earth! by dani gilad

dani gilad — Sun, 18 Jul 2010 09:56:06 +0000

RSS (most commonly expanded as Really Simple Syndication) is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format. An RSS document (which is called a “feed”, “web feed”, or “channel”) includes full or summarized text, plus metadata such as publishing dates and authorship. Web feeds benefit publishers by letting them syndicate content automatically. They benefit readers who want to subscribe to timely updates from favored websites or to aggregate feeds from many sites into one place. RSS feeds can be read using software called an “RSS reader”, “feed reader”, or “aggregator”, which can be web-based, desktop-based, or mobile-device-based.
Event ranges from box-lunch drop-off to full-service catering. Caterers (????????)and their staff are part of the food service industry. When most people refer to a “caterer”, they are referring to an event caterer who serves food with waiting staff at dining tables or sets up a self-serve buffet.

Comment on Performance impact of the readonly keyword by Andrei Rinea

Andrei Rinea — Wed, 17 Mar 2010 08:38:54 +0000

Maybe your co-worker was confusing readonly with const.

That would make a lot of sense..

Comment on AutoResetEvent vs ManualResetEvent: beware! by ???????? ????

???????? ???? — Wed, 06 Jan 2010 15:07:18 +0000

Just imagine that the AutoResetEvent executes WaitOne() and Reset() as a single atomic operation.
thanks for the great article!

Comment on Choosing composition over inheritance: yet another example! by ??????

?????? — Wed, 21 Oct 2009 13:25:58 +0000

???? ??? ?????

Comment on AutoResetEvent vs ManualResetEvent: beware! by Anonymous

Anonymous — Fri, 18 Sep 2009 13:33:00 +0000

If AutoresetEvent’s Set is Called when it is not required, then there is no use of Waitone in the thread.. Beaware of it folks !!!

Comment on AutoResetEvent vs ManualResetEvent: beware! by Anonymous

Anonymous — Fri, 18 Sep 2009 13:31:50 +0000

Yes u r right.. but there is one more problem here in AutoresetEvent’s
Set Method.. It has to be called when it is needed. if not again u will get into trouble.

Comment on Choosing composition over inheritance: yet another example! by Naveena

Naveena — Wed, 01 Apr 2009 22:04:44 +0000

Simple example.. thanks

Comment on Choosing composition over inheritance: yet another example! by Anonymous

Anonymous — Wed, 01 Apr 2009 22:04:09 +0000

Excellent

Comment on Choosing composition over inheritance: yet another example! by Julien

Julien — Fri, 13 Mar 2009 06:41:54 +0000

It certainly was, my apologies !
I’ll fix it right now !

Comment on Choosing composition over inheritance: yet another example! by brad

brad — Thu, 12 Mar 2009 15:03:07 +0000

That’s what I thought, but the trip constructor that takes three arguments is assigned protected not public. If I change your example to public, it works fine. Was protected a mistype?

Comment on Choosing composition over inheritance: yet another example! by Julien

Julien — Thu, 12 Mar 2009 08:20:40 +0000

You would not use directry an instance of ITransportationMode, you would inject it in the Trip class like this :

Trip tripToParis = new Trip(”barcelona”, “paris”, new PlaneTransportationMode());
DateTime arrivalTime = tripToParis.CalculateEstimatedArrivalTime()

The point is that this calculation can change and it should not be the responsability of the Trip class to perform it. Therefore, the best way to change the behavior of the trip class is not through inheritance but through composition.

Now, keep in mind that this example is very basic and in a real application you would have real logic in CalculateTransportationTimeBetween() :)

Comment on Choosing composition over inheritance: yet another example! by brad

brad — Wed, 11 Mar 2009 13:25:05 +0000

how do you run this code?

CarTransportationMode c = new CarTransportationMode();
TimeSpan s = c.CalculateTransportationTimeBetween(”", “”);

I don’t see where the Trip class is used or the benefits of this?

Comment on Choosing composition over inheritance: yet another example! by Nick Wiggill

Nick Wiggill — Sat, 14 Feb 2009 14:31:58 +0000

Here’s another example:

http://www.visualharmonics.co.uk/actionscript-3/using-function-closures-in-object-composition/

Comment on Choosing composition over inheritance: yet another example! by Nick Wiggill

Nick Wiggill — Wed, 11 Feb 2009 20:24:14 +0000

Excellent, thanks for a simple example Julien.

Comment on Choosing composition over inheritance: yet another example! by Thomas Jensen

Thomas Jensen — Fri, 06 Feb 2009 22:30:51 +0000

Thanks…:)

Comment on AutoResetEvent vs ManualResetEvent: beware! by Guimasun

Guimasun — Mon, 30 Jun 2008 14:33:50 +0000

The same happened to me. I was using a AutoResentEvent to sinalize thread termination, but sometimes the condition had been tested inside the thread loop which resets the event, so the while condition would never end.
Cheers

Comment on The null singleton by Julien

Julien — Mon, 26 May 2008 12:50:39 +0000

Multithreading is definitely an issue with singletons: most of the time, the implementation is not thread safe which can result in a “lost” instance as you were saying. Even if garbage collection is there, it can have several nasty effects depending on the context. For instance, the second instance created can try to access something that will be locked by the first instance and then fail to instantiate itself properly.

Concerning your way to initialize the singleton, I think it will be thread safe because a static field is only populated once by the CLR. However, the problem is that the instance will be created as soon something from the class is called for the first time. Therefore, you have even less control on when the instance will be created (but that might be perfectly acceptable :)). Using a static constructor might also be problematic. In that case, the instance will be created when the class is accessed but if an exception happens in the static constructor, it will be rethrown as a TypeInitializationException which would be a bit surprising I guess. More information here.

Finally, disposing a singleton is not something I’ve seen before and I would even say that it’s probably a code-smell. As a matter of fact, I don’t think you should dispose a singleton during the lifetime of the program. You might want to reset the state of the singleton somehow, but not dispose it. If you need to dispose it before the end of the program, you might end up with dozens or hundreds of initializations of your singleton… it will be totally uncontrolled. If you’re at the end of the lifetime of the program, then it’s not really a big deal because the CLR will release all the resources for you anyway.

Comment on The null singleton by agamemnon

agamemnon — Mon, 26 May 2008 08:49:32 +0000

Hello Julien,

I have few remarks about instance initialization in singleton. Concurrency access and instance creation are often forgotten when using this design pattern. This can lead to the creation of more than one instance (but thanks to the garbage collector if available, only one will be kept).
The second remark is rather a question. The class instance can be created in class loading time with a static block like this : private static Singleton instance = new Singleton();
This creation method can solve some extra cost when managing the concurrent access to the instance, but is it safe to use it? (I have some doubts about dll loading order and instances creation).
You mention the case where we have a large number of singleton. I have noticed in the software I’m working on it is that there is no method to free the instance.

Regards