--part1_1a5.79ae78f.2aa00829_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
> But do not forget that using of VXCMD or V4RB API will make your app easy
> modified from embedded engine version to client version.
>
This is true, but also remember we can write a wrapper to work with old API.
For example:
function Valentina theCmd
global valentina_server
switch(theCmd)
case "Database_SQLSelect"
open socket to valentina_server
write sqlCmd to socket valentina_server
put param(2) into theSQL
write theSQL to socket valentina_server
read from socket valentina_server until empty
put it into theCursor
close socket valentina_server
return theCursor
break
end switch
end Valentina
Of course I am not suggesting we trash VXCMD or V4RB, just excited by the
possibilities of socket access.
Also this would mean that Valentina developers can write cgi scripts that run
on machines where they are not allowed to install add-ons like VXCMD. Almost
all services will give you Perl, PHP, etc, but many will be a pain in the
neck if you want to install something of your own. The net result would be
that I, a Valentina developer, could buy hosting service anywhere with
standard tools and access my Valentina Server elsewhere.
Anyway, I hope keeping a clear, open protocol would have many benefits and no
drawbacks for Valentina Server.
Brian
--part1_1a5.79ae78f.2aa00829_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><BLOCKQUOTE CITE STYLE="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px" TYPE="CITE"><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2" STYLE="BACKGROUND-COLOR: #FFFFFF">
But do not forget that using of VXCMD or V4RB API will make your app easy<BR>
modified from embedded engine version to client version.</FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2" STYLE="BACKGROUND-COLOR: #FFFFFF"><BR>
</BLOCKQUOTE></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2" STYLE="BACKGROUND-COLOR: #FFFFFF"><BR>
This is true, but also remember we can write a wrapper to work with old API.<BR>
For example:<BR>
<BR>
function Valentina theCmd<BR>
<BR>
global valentina_server<BR>
<BR>
switch(theCmd)<BR>
case "Database_SQLSelect"<BR>
open socket to valentina_server<BR>
write sqlCmd to socket valentina_server<BR>
put param(2) into theSQL<BR>
write theSQL to socket valentina_server<BR>
read from socket valentina_server until empty<BR>
put it into theCursor<BR>
close socket valentina_server<BR>
return theCursor<BR>
break <BR>
end switch<BR>
end Valentina<BR>
</FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2" STYLE="BACKGROUND-COLOR: #FFFFFF"><BR>
Of course I am not suggesting we trash VXCMD or V4RB, just excited by the possibilities of socket access. <BR>
Also this would mean that Valentina developers can write cgi scripts that run on machines where they are not allowed to install add-ons like VXCMD. Almost all services will give you Perl, PHP, etc, but many will be a pain in the neck if you want to instal
l something of your own. The net result would be that I, a Valentina developer, could buy hosting service anywhere with standard tools and access my Valentina Server elsewhere.<BR>
<BR>
Anyway, I hope keeping a clear, open protocol would have many benefits and no drawbacks for Valentina Server.<BR>
<BR>
Brian</FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2" STYLE="BACKGROUND-COLOR: #FFFFFF"></FONT></HTML>
--part1_1a5.79ae78f.2aa00829_boundary--
--part1_1a5.79ae78f.2aa00829_boundary
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
©2002 Yennie At aol DOT com |
