.NET Blogging Tool Saga Cont'd - Part 2
.NET Blogging Tool Saga Cont'd - Part 2
Except that my web server already has ASP.net. I get a few hundred hits a day. What do I care? :-) I understand what motivates someone like Dave to make it just require FTP and no active server components. He has a monetary interest in working with the largest crowd possible. Personally, I don't have any such need. I'd rather prefer something powerful and dynamic over something static and flaky, but that's just me. :-) [The .NET Guy]
You're right. That's the only real difference between a power user and a typical end user. So it's just a question of target audience.
Technically, most of the code could be shared with the decision of when the content is generated being the only thing done differently. Obviously the content generation engine and database manipualation could be the same. It's just a matter of when the content engine is executed and what is done with the results. In the "desktop publishing" scenario it's executed for all posts, over all categories, each time a new post is published. In the "on demand" scenario, there's some sort of timestamp kept in the database that the IHttpHandler would check against the date of the file on the system (if it even existed) to determine if it needs to be regenerated.
Just some thoughts... maybe one day one of us will actually find the time to put this thing together. ;)