I have done some work aimed at just that with my work-in-progress-but-stalled 
serverTasks fileI/O widget. Here's my dev ref spec if anybody want to pick up on it 
for server-side languages besides ASP, which unfortunatly is the only one I'm 
profident enough in:

input
=====
querystring from a form with get method or manipulating the URI with javascript: 

file  - the file path + name 
task  - values: open|save|del
content  - text to be saved (not required for open or del,so the script  
   shouldn't bug out if this one isn't provided)

output
=======
javascript syntax variables new values as pure text without any surrounding script tag:

this.file  - just to reassure it's the right file being handled 
this.task  - the current set task (which will be default til new is set) 
this.scriptname  - returns the scriptname just to make sure
this.serverResponse - returns "opened","saved" or "deleted" if successful or else 
custom error message
this.tasktime  - nice feature if you want to inform your users how long they waited ;)
this.content  - holds the last saved content until the variable value is changed 
(escape encoded)


script-run
==========
the script should run this:

1. recieve the input (if applicable set to local values)
2. read from file opendir and compare if any line match the path ( ievalue of file 
input value excluding the filename - the part before last /). If it match any one line 
the script should continue towards running the task, and if not just end and return 
new output this.serverResponse='no access'.
3. check that the file exists. If it doesn't, task save should create a new file, 
while open and del just return serverResponse='non-existing'.
4. run the task defined in input variable task. task save should return 'saved' if 
successful, task open return 'opened' & task del 'deleted'.
5 output javascript syntax as pure text, the content value should be escape encoded as 
to not mess upp the browser client view  


I'm not yet sure how the javascript would have to be output to work correctly in the 
loadpanel of the serverTask fileI/O widget, but it should be able to get the same 
output from whatever server-side language using the standard model above, and even a 
client-side script might interface it as complement when.

I already got it partly working as expected with the ASP variant, all i need is some 
ideas as to how to get the javascript properly refered back to the widget in which the 
hidden loadpanel holds the ASP script output. And of course if someone would take on 
the task of scripting a corresponding server-side variant of that interface as 
described above. Then maybe it could be taken further to a dbI/O servertasks widget 
later on...

You're free to ask or comment ahead, all responses are apprieated :)

Henrik Våglin [ [EMAIL PROTECTED] ]

----- Original Message ----- 
From: "Robert Rainwater" <[EMAIL PROTECTED]>
To: "DynAPI Development List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 14, 2001 9:25 PM
Subject: Re[2]: [Dynapi-Dev] serious, ... really!


> 
> We should come up with some specification for the component, including
> the methods and properties.  Then, it could be created for different
> environments, but work essentially the same.  That way, people could
> help work on the specific language that they know the best.
> 
> -- 
> // Robert Rainwater
> 
> On 2/14/2001, 2:09:52 PM EST, Doug wrote about "[Dynapi-Dev] serious, ... really!":
> 
> > What about those who don't use unix?
> > How about a perl based DynServer component?
> > We could implement Server-side File i/o, as well as a Perl based Database..
> > To name a couple of things
> > ----- Original Message -----
> > From: "Raymond Smith" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, February 13, 2001 4:29 PM
> > Subject: [Dynapi-Dev] serious, ... really!
> 
> 
> >> Associates,
> >>
> >> I've been doing alot of research in what direction I would like to go
> > next;
> >> in conjunction with the DynAPI.  While the API is wonderous for creating
> >> dynamic interfaces it needs a server-side partner in my mind to reach its
> >> full potential.
> >>
> >> Comparing ASP, JSP and PHP I've decided that LAMP (Linux, Apache, mySQL
> > and
> >> PHP) tends to result in more robust client/server applications.  With PHP
> >> Zend boosted beating both in speed and performance and PHP appears to have
> >> allot of energy surronding it at this time.
> >>
> >> So, from that aspect, PHP wins.  Also there appears to be a very sizable
> >> family of "real" PHP initiatives on Source Forge to draw and learn from.
> >>
> >> But,...
> >>
> >> From my readings it's also apparent that JAVA is "king and master" of the
> >> Server Side Application if the JVM and runtime code is compiled properly.
> >> But, checking Source Forge for Java related projects creates a large list
> > of
> >> mostly abstract and esoteric projects: not alot of meat on the bones from
> > a
> >> "get things done" standpoint.
> >>
> >> Question is, what do you mavens of logical mayhem recommend as my next
> > area
> >> of focus.  I am interested in developing some server-side applications
> > that
> >> meld into the DynAPI interface on the client-side (yes, Pascal... be
> >> amazied).
> >>
> >> Java or PHP?
> >>
> >> Will learning PHP now be advantageous or detrimental to learning JAVA/JINI
> >> later?
> >> How does OOP in PHP compare to JAVA OOP?  I realize it lacks interfaces
> > and
> >> solid abstraction.
> >> Why are most the PHP initiatives on Source Forge solid and down to earth
> >> while JAVA tends to be lofty and not very "real world" in nature?
> >>
> >> Looking for a little feedback here.
> >>
> >> Thanks,
> >>
> >> Ray "fear the rock" Smith
> >>
> >>
> >> _______________________________________________
> >> Dynapi-Dev mailing list
> >> [EMAIL PROTECTED]
> >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> 
> 
> > ---
> > Outgoing mail is certified Virus Free by AVG Free Edition
> > http://www.grisoft.com/html/us_index.cfm
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01
> 
> 
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev 
> 
> 
> ----------------------
> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
> DynAPI Homepage: http://dynapi.sourceforge.net/
> 
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> 


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to