AK's weblog

Entries tagged as cms

Saturday, September 24. 2005

Request for improvements: URL decoder

As the observing readers of my weblog already I know, I'm working on an HTTP stack as part of a high-performance Ruby servlet container that I want to implement. This weekend, I finished the work on the HTTP stack, and the tests so far look good, so everything seems quite stable. That means: refactoring. Currently, there's only one piece of code that doesn't look to good in my eyes, as it is to "un-C++-ish", but as I'm not a regular user of the C++ language and especially its standard library, and have no good ideas how.

That piece of code is an URL decoder, and looks like the following:

static inline int h2c(char hi, char lo) {
std::string s;
int value = util::PARSE_FAILED;
s += hi;
s += lo;
std::istringstream is(s);
is >> std::hex >> value;
return value;
}
std::string util::url_decode(const std::string& s) {
std::string result;
std::istringstream iss(s);
char c;
for (iss >> c;!iss.eof();iss >> c) {
if ('+' == c) {
result += ' ';
} else if ('%' == c) {
char c1 = 0, c2 = 0;
iss >> c1;
iss >> c2;
if (!iss.eof()) {
int r = h2c(c1,c2);
if (r != PARSE_FAILED) {
result += static_cast<char>(r);
}
}
} else {
result += c;
}
}
return result;
}

Any recommendations?

Posted by admin at 19:16 | Comments (3) | Trackbacks (0)

Defined tags for this entry: c++, cms, programming, refactoring

Saturday, September 17. 2005

News from the CMS front

In this blog, I already wrote about developing a new content management system. Well, after doing some research, I concluded that, in order to get a reasonable performance, I need to develop a high-performance servlet container for Ruby (think of Tomcat for Ruby).

I evaluated a few available ready-to-use HTTP server stacks, but I liked none of them (I was always forced to use threads), so I decided to develop my own one, in C++. Currently, I'm at an early level, all I've got is a nice and easy-to-use wrapper around Unix sockets, providing only the socket functionality that I need. But a nice feature is that it enables me to do the network communication via C++ iostreams. Yes, that's right, no more low-level read()/write()/send()/recv()/whatever.

Posted by admin at 15:28 | Comment (1) | Trackbacks (0)

Defined tags for this entry: c++, cms, programming, ruby

Monday, August 15. 2005

Refined CMS proposal

Although the last week was quity stressy, I found some time to extend my proposal on developing a new CMS. You can find it here. Comments are welcome.

What has changed since the first proposal? Well, I wrote more about the proposed programmability, including eRuby example code of possible use cases, including the XML integration (people would also like to store structured data, after all...). I also wrote something about logically separating the different parts into so-called "facilities" each of which has a different responsibility, including an (incomplete) example XML-RPC interface how it might look like.

Posted by Andreas Krennmair at 16:33 | Comments (0) | Trackbacks (0)

Defined tags for this entry: cms

Sunday, August 7. 2005

Proposal for a new CMS

After I saw the Stellent Content Server at a customer, I thought about developing my own programmable CMS, because I liked some of the ideas. After thinking about all that for some time, I'm currently quite clear about how the overall principles and the design should look. I wrote down an overview about the general concepts, which you can find here.

I'm asking everyone for feedback. Please be aware that the explicit goal is not to create yet another easy-to-use CMS, but instead to provide a CMS that can stand up to high demands on programmability, flexibility and scalability, even with huge amounts of data.

Posted by Andreas Krennmair at 20:22 | Comment (1) | Trackbacks (0)

Defined tags for this entry: cms, idea

(Page 1 of 1, totaling 4 entries)