Looks like pretty nice code. I gather tempscripts (tempscripts.tar.gz) are perl scripts to add data to a SQL database.
The PHP code runs the web interface and gathers data from the database.
Using a database as the intermediary makes sense. A clear separation of
function. You can also manage permissions a little more simply.
You use the fuse filesystem as the interface to 1-wire.. This has good points
and bad points. It's certainly stable (I've had it run 9 months straight without
problems), but requires fuse and proper file permissions. You could use owperl,
and access 1-wire directly. This is a little inefficient unless you make your
perl script persistent (loop and sleep). Your current technique seems to be to
use cron to start the data gathering, in which case the filesystem is a good
choice.
If you want remote monitoring, there are several choices:
1. A remote server (even an appliance like the NSLU2) and use owserver to
connect to owfs locally.
2. A remocte server and use the database access function over the net.
You can even use a combination.
Also, if you want to pool data from more than one location, run owserver at
each, and owfs locally can connect to several.
Paul
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Jim Canfield
Sent: Mon 5/15/2006 4:51 PM
To: owfs-developers@lists.sourceforge.net
Subject: [Owfs-developers] OWFS - Temp Trakker Source
Greetings,
I have decided to post the source to the web app I created last year.
It's not pretty, but it will be a start. You can find it here:
http://tshweb.olympiamd.com/temp/
With any luck I should be able to set this up as a project on sourceforge.
The framework I used for the web app is Gregory Engel's Web Application
Gateway (WAG).
http://wag.javazen.org/
You will find the meat of the application in the apps/temp directory.
Also notice a tarball of perl scripts they run most of the
backend functions. The PHP simply displays DB info. After looking
at them I'm sure you will quickly note there are much more efficient
ways of going things. I'll be very interested to get others input.
Here are my short term goals:
- Make this a pluggable app for any machine running owfs supporting
php/mysql.
- Clean up WAG code...there is a lot of unused code just sitting out there.
- Abandon the net4801. I realize now there are much better ways to
configure an embedded device and much of that will take time and money.
I'd rather focus on a clean OWFS front-end that will be useful to a
broader audience. Also, with OWFS now existing as distributed system, I
see no real need for anything more then the 1-wire wireless routers and
the e-link hubs.
- Create install scripts (I'm clueless in this area.)
Comments welcome.
Jim
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
<<winmail.dat>>
