Hardware Failure:Say Goodbye for my ADSL2+ Router
Around 2006, I bought this zyxel router.That is quite good, it has a web interface. Moreover, it has a command console to set advance configurations, such as loopback. That is quite good. However, recently, the internet kept to drop off. I needed to reset the router. A few days, the router was completely "melt down", DSL light was off and power light kept to flashing. In addition, I typed the router ip and try to login there. That was not working at all. That is 6 years time, I think the lifespan of router reached the limit. Finally, I had to say goodbye to it. It did a great job!
After that, I got a router and gigabit Ethernet switch! That is a time to upgrade too!
Cloud Servers
Recently, I have a lot of clients moved their services to cloud services, they are trying to remove their server rack. That is good for small businesses, they don't need to spend the money to maintain their servers. But the cloud backup storage is relative expensive and that is not very fast to get the data from servers via broadband. Thus, there is still some draw back.
Singleton in C#
To implement Singleton Pattern in C#, that is easy. I like to static class. For example:
Code
public static class GobalData | |
{ | |
public static Group Group {get;set;} | |
} |
Not found c:\preload\convert.cmd in ThninkPad
My friend brought a ThinkPad SL500 to me. The login password are changed by somethings, that sounds some virus in there. I decided to rebuild the machine. So, I pressed F11 during the startup to enter the recovery center. Then I choose the option to recover the machine with factory setting, I got the message "Not found c:\preload\convert.cmd ". I phoned their helpdesk, I have been told that is because of recovery partition are missing. Thus, the only way to grab a recovery disk from Lenovo.
The reason to use repository pattern
In our AdvGenCMS, we use the repository pattern in the data layer. Inside each repository, there is a LINQ datacontext. We are completely hiding the LINQ from the upper layers. In this way, we can switch to use another ORM technology in the future without other layers. We need to the repositories. That is the reason to use repository pattern