Are you too lazy to ssh into servers you’re monitoring? Do you not want to set up a slick page with SNMP and/or RRDTool? Or, do these solutions just not fit your needs?
TopJax might be for you.
TopJax is essentially the “top” unix utility ported to the web via Ajax using Sack of Ajax. It provides the ability to view system processes, sort processes by various fields, pause/unpause monitoring, and hide idle processes.
TopJax is released under the GPL.
Note: This is probably highly insecure. I don’t encourage you to run it on a public server.
The permanent address for TopJax is http://emergent.urbanpug.com/topjax
If you’d like to keep up-to-date on the progress of the project, you can subscribe to this site’s RSS feed –
Notes: I’ve separated all styling information from the code, because I know I’m not the best person with CSS. If anyone wants to help by providing alternate stylesheets, I’d be very happy.
If you want to help out by making a small donation, that would be cool.
You could also buy a Threadless shirt using me as a referral.
Here’s a concept, one that i’ve been toying around with myself, actually (more to come soon on my end) — It’s WebCmd — It’s an ajax-based command line. It uses perl + libXmlRequest to produce a “remote command line in a browser” — which is something that would have previously been unheard of without using java, say, oh, 2 days ago.
What does this actually get you? Well, alone, you might be able to do some system administration w/o having to use SSH, which might be an “ok” thing — but really, the key concept is really to provide a new way of accessing old applications. I know there are companies out there that have been really pushing hard to get old green screen applications pushed into the present by doing various things like wrapping the old “screens” in HTML, using java to interface w/ the old application, providing a slightly fancier interface to the old app.
Now everyone’s got a new choice for doing this kind of thing. What i’m more interested, being a linux guy, is the ability to do with ajaxified methods some of the basic things i would normally have to do by opening up a shell, logging into a server, and running some commands.
I’m working on a little utility that i myself will find useful, and i hope others will too.
Both of these are added to the Ajax Toolkit and Project List. I think i’m going to start calling it something else — maybe “rich web framework toolkit and project list” — because it doesn’t really cover “just” ajax anymore.
Ok, I understand that Sabre used the word ‘Rico’ to mean that they’ve got a framework for ‘rich applications.’ However, whenever i read or hear about rico, i can’t help but think of one of two things.
- Tony Soprano — How many times do you hear the mobsters mention the ‘RICO’ laws?
- Rico….. Suave!
Now, I think Rico is exactly what the “Rich Web Application” community needs. Not because of what it is, but because of who is behind it. Sabre is a fairly large company, and they’ve been sponsoring Rico, finally releasing it into the wild. It’s nice that toolkits exist, but you really need an all-encompassing package that supports lots of functionality.
It’s hard to develop an application with lots of little pieces. Prototype is nice, but it doesn’t have all the pieces there. Backbase is great, but it’s not open source, and costs some real money. Dojo will be nice, when/if it gets here. I’m not criticizing, they’re new — they just need time to get everything put together.
For something as complicated as a rich web app framework, you really need some financial backing to put enough people on the project to make it worthwhile. Lone developers go so far, but we need more. I think that’s what we’ve got with Rico. Dojo might have it, i’m not sure how many people from Jot work on Dojo, and how much money Jot has / will have to develop with.
Anyway, I think Sabre’s shown some “enlightened self interest” with releasing Rico, and I think that it’s going to take the web app framework community to new, very good, places.
I’ve added qooxdoo to the list of toolkits, and it got me thinking. With dojo, qooxdoo, all the ajax frameworks out there, etc., we’re really in the infancy of a new breed of web applications.
Yes, google’s got em already, but the average joe doesn’t have the manpower to put all the pieces together himself. These toolkits are still very rough around the edges, and it’s going to take some time and some painful development of applications, some aborted projects, some cross-flow of ideas between projects, but we’ll see the browser be what microsoft feared it would be from the beginning — the browser is going to become the platform.
Why is this happening? We’re at a point now where the tools for web development, your databases and your server side scripting languages / application servers are already written, and they’re pretty good. me, as a developer, I can’t go out and hack together a PHP/FI version 1.0 and have it be of any use to anyone. What I’m saying is that because the tools are there, we’re now able to build tools on top of our tools, to make what we build even better.
Now, i haven’t actually played with the likes of Backbase, and they might be closer than anyone, I just don’t know. I think a project for tomorrow is to go download the backbase community edition and see what i can do.
Added AjaxAC to the toolkit list. It’s yet another ajax toolkit. What I like about AjaxAC is their demo, which is a Country/City/State finder that loads data as you make selections.