Rough draft:Add
your comments and suggestions,then
we'll make a second draft and do it again. DataBase
access:
-SQL implementation (rip code from or modify MySQL?)
Why not just build a (sql) data
request interpreter on the server. I don't believe that all users of DynAPI
will need the use of a database connection. I perfer ODBC with PERL(DBI/DBD).
This allows for the option of using any (and there are alot)
SQL format that is supported by PERL (just about all the major vendors
and freeware)
I know that someone is going to
want to slap me, but what about a simplified version for flat file storage?
-getField('fieldname')
> get the value in field 'fieldname' for
the selected record
-setField('fieldname')
> set the value in field
'fieldname' for the selected record
-SQLExecute('sqlstring')
> you would pass your
"SELECT * FROM" or
"DELETE ALL FOR"
Don't forget CREATE
statements to the DB
engine here.. File
I/O (server-side):
-directory navigation:
+Server(s) ??
+list files
+change working dir
-file streaming:
+Open file stream
+get X bytes from file stream
+get ALL from file stream
+write to file stream: append/insert/overwrite
+close file stream
-file manipulation:
+copy file
+move file
+rename file
+delete file
+maybe batch versions of the above
(ie myFileStreamObject.rename('f*s.js','f*r.js') ) Network
Comm: Not sure what
you would want for network comm..But
I was thinking, you can make tcpip connections with an applet right?So,
on thos platforms that don't support, say, LiveConnect for instance,your
applet can make a network connection to you serv-side component,which
would then instruct you DynaPI to do something(using
a queue I would assume as you can't 'tell' jscript to do anything from
the server...)
Accessing Mutilple (SQL) servers will defintely come up somewhere
during this discussion, although this could be handled from the backend
where possible, there will be instances where it would be needed.
It this the first posting to this thread? Are you just looking for
SQL feedback, or other things?
bobb
