.NET and Java J2EE

.NET and Java J2EE I have been looking into .NET recently.  Yes.. I am finally looking.  Was trying to look into .NET for the last couple of years… but was always trying.  Finally, when a person gets stuck in Pakistan with no movies, no bridge, no friends for coffeeshop chats, he has time to do some serious investigation into software technologies…

I think this point is pretty obvious.. I mean.. just look at the number of articles I have written recently.  Scary really.  Anyway, this will be a constantly updated article.  Why constantly updated?

Well, for the simple reason that I am not exactly looking at mastering .NET within a day or two.. and this is intended to be some sort of a journal for me to note down the difference between the 2 frameworks.  I am pretty familiar with Java J2EE… so I should be able to point out the difference along the way….

Stay tuned. :P

Availability of Cache in .NET

In Java, the basic framework comes with:

  • Page
  • Request
  • Session
  • Application

In .NET, it comes with a default implementation of a caching system.   Some data are just meant to be cached to prevent overloading of the database with unnecessary hits.  In Java, caches are generally implemented through a separate component like EhCache (something employed by hibernate).  However, in .NET, they make it a lot more convenient by including it as part of the default framework.

 

Cache.Add(“mycache”, myobj, null, DateTime.MaxValue, TimeSpan.FromMinutes(10), CacheItemPriority.Normal, null);

Leave a Reply

You must be logged in to post a comment.