Hi Andrew,
regarding exchange of OIO forms. I presume that these forms are specific to
the OIO format. This means that foreign applications that do not use your
form format or do not generate similar forms may not need to call them.
May I forward my thoughts on this?
a) We can create a special dictionary for your OIO forms procedure call and we
might name it something like OIO-HXP procedure call dictionary.
b) All OIO specific calls will be prepended with OIO. like:
OIO.Form.Get
OIO.Form.Save
OIO.Document.Get
OIO.Document.Save
OIO.xxxxx.xxxx
c) All these procedures will be supported in a separate server other than
"server". e.g.
--/hxp/oio.php
--/hxp/oio.py
--/hxp/oio.cgi
--/hxp/oio.pl
--/hxp/etc......
d) It is not compulsory to include these procedures in the default main server
e.g. "server.py" or "server.php"
c) However, the default server MUST support a system call which returns a
true/false telling the remote client whether the server is supporting the OIO
calls.
d) A suggested system call for this is: System.Server.OIO.Exists
return type is boolen.
e) the remote client should access first the default server and call this
procedure. If the return is true then he switches to the "OIO.xxx" server and
start calling the OIO procedures. If the return is false, then he either
stops communicating or just access the default server and call the default
procedures e.g. Person.Basic, Person.PID.List, etc.
Please let me know your own views on this.
Thanks a lot.
elpidio
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Hxp-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hxp-developers
