| Cozta Norhalim's profilecozta.netBlogLists | Help |
Covalentia Version 2.1 Release Candidate 1As promised, I’ve uploaded a new release candidate, Covalentia Version 2.1 RC 1 to both Covalentia Community Portal and CodePlex site. This release includes:
If you encounter any problems, don’t hesitate to e-mail me. Enjoy Covalentia Community Portal Goes OnlineFinally! It’s up and running, and I’d really like to apologize to my fellow programmers for any inconvenience caused.
On another note, I’m going to upload a new release candidate, Covalentia Version 2.1 RC 1 by today or tomorrow. This release will have a slightly new look and contain the source codes for the Covalentia.Core project. I shall discuss the details later. So, stay tuned DRAGONThat's the name of our server
Perhaps, LAME is more appropriate. I'm thinking of adding more RAM to it, say another 256 or 512 MB, if I can find one in the unused Red Hat machine. Server ReinstallationThe Covalentia community portal will be offline for a few more days because the lame server is currently with me, and not at the data center. I’m backing-up all the files and reinstalling everything from scratch. Take a look at the specs (and try not to laugh):
So, now you know why we need fund Next ReleaseThere are quite a number of minor changes in the upcoming release of Covalentia Version 2.1. In the last few days, I’ve been working on code and database optimizations, naming convention, fixing bugs and GUIs. The new release will also include the source codes of Covalentia.Core project which contains the Data Access Layer and other core components. With the availability of these source codes, developers can see what’s really going on (or nothing’s going on) behind the curtains and perhaps learn a few things (or teach me if I did wrong) about System.Reflection which is heavily being used and how to avoid multiple expensive calls to this class using cache. And more importantly, it should give those greedy hackers less reason to get into our community server. I’ve given everything for FREE. I left nothing. I have nothing left ;)
Updates
To Dos
As for our community server, our hope to bring it online last week was dashed. The server is infected with all kinds of spy-wares and ad-wares. We’re in the process of removing them and we’ll let you know once it’s stable. Somebody actually unplugged the firewall and chaos reigned for a while. It's a war. We eventually managed to put a stop to it but not without casualty on our side. But, we’ll continue to survive ;) Upgrading WorkWe are currently upgrading our server at Covalent Technology. Hence, the Covalentia community portal and other sites that we’re hosting will remain offline for a few days. We hope to bring it up as soon as we can. I suspect some virus attack and network card problem. In the past few weeks, we’re experiencing malicious hacking attempts, and perhaps one (or more) of these attempts had been successful. I really don’t see the reason why people would do such things to us. But, I do know a few why people would not. First of all, we’re not a multimillion company, and thus, these hackers will not profit from us because we won’t be able to hire them to boost up our server security. Second, we’re giving Covalentia for FREE along with the source codes. And finally, if these hackers would just ask us which part of Covalentia (or us) that they want, we’d be more than willing to give them so
Just ask, you greedy bastards. Lost Connection when Running MyISAM and InnoDB Databases SilmultaneouslyA few weeks ago I posted this error I'm experiencing when running my .NET applications on Windows Server 2000 or XP on MySQL Forum. I’ve totally forgotten about it until today, and realize that someone from MySQL has actually replied to my posting. He suggested that I report a bug which I just did. If you encounter the same problem, perhaps you may want to keep track the bug here.
If you don't believe me, try out some of my previous applications running MyISAM databases. After a while, you'll get the error. And there's nothing wrong with my applications, trust me. It's a MySQL bug |
|
|