Page 1 of 1

Why Awasu is Different

Posted: Mon Oct 27, 2003 12:51 am
by Guest
To whom it may concern.

I've been messing around with RSS stuff now for several months. Probably the most frustrating thing was very clear... it was the most frustrating when I started investigating this world, and it still is. Perhaps some of you may have experienced it as well. I am talking about software out there that makes "claims", but when you actually download it and use it... lookout. There are so many things out there on RSS news readers... it's a real maze. The situation I am in, is very different, because I want to make the massive news gathering simple, and then wade through it quickly, picking what I want, and then uploading it to a web site. Sounds simple, huh? Wrong.

The ONLY software I have found out there that can at least provide an open door to do this is Awasu. Simply stated, Awasu has some major features that very few have. These are greeeaat for developers and people who are managing content:

1) There is not an "annual" membership
2) It is not an online application, i.e., remote server storage
3) It actually stores data files in the program directory that are relevant
4) Fairly simple and un-convoluted (many are confusing)
5) The ability to "mark" and/or seclude various ARTICLES (not feeds)

Hey it's Really Simple Syndication... so the application should be "really simple" too, huh?

Now if you have ever done any web content mangement, you should see this, especially #3 and #5. Yes... now I can actually write an application to grab those data files and send them to my database.

Here is the opportunity for Awasu:
You can do something that NOBODY does. That is, make the favorite or read selections that are sequestered more sophisticated. GRANTED NOBODY EVEN HAS THE SIMPLE THING YOU HAVE IN THERE NOW... BUT, if you make this step, you will enable web content adminstrators to partition out their data for EACH SITE, i.e, separate content. Better yet... why not just use a list box control or something with checkboxes RIGHT NEXT TO THE ARTICLE, i.e., "keep this article", or "send this article to ABC Folder." I just can't understand why nobody sees this yet... perhaps developing for "developers" is a tough business. It's a way of content management at a very simple level for people of all types... BUT DOES NOT EXIST TODAY... (in a client environment, at least from what I have found yet).

Second, you could do what I am doing (getting ready to do)... which is simply take the generated files and send them to your database. Perhaps use a cheapo client database... then create a connection wizard or something with IP and user/pass to a SQL Server database on the web... you have standard table protocols and let it rip. If done properly then... when those links are hit on the web site you can set up a counter. e.g., if someone is hitting an old article a zillion times a day... why take it down?

diver

Re: Why Awasu is Different

Posted: Mon Oct 27, 2003 9:49 am
by support
Anonymous wrote:Second, you could do what I am doing (getting ready to do)... which is simply take the generated files and send them to your database. Perhaps use a cheapo client database... then create a connection wizard or something with IP and user/pass to a SQL Server database on the web... you have standard table protocols and let it rip. If done properly then... when those links are hit on the web site you can set up a counter. e.g., if someone is hitting an old article a zillion times a day... why take it down?


Cool. It sounds like you've got some excellent ideas for building on top of Awasu. That is something we've always been very keen to see people do and we have tried hard to make it possible with Awasu's plugin architecture.

There is already a project underway where a channel hook is being written to receive new content as it arrives and put it into a database e.g. MySQL or Sleepycat. Add an interface to query it and you have a seriously powerful content management system.

Let us know if you're interested in getting involved.