You could approach this in an n-tiered manner which addresses both the speed
and security issues.  Your VB client would use HTTPS to make a request of
your web server.  The web server invokes VB and UniObjects to access
Universe.  This eliminates direct exposure of the Universe box to the
internet.  Various techniques are available for optimizing the web
components, connection pooling, etc.

When you say "VB", if you're talking VB.NET then you have a couple options.
Of course there is the existing PDP.NET from Raining Data, which is used in
many U2 sites for intranet and extranet apps.  (Contact me for details.)
You can also look forward to UO.NET: Why code in old VB with old UO when new
tools are coming available that are so much better?

Consider Web Services rather than hardcoding all of your data access logic
into the client.  That will allow you much more versatility in future
development.  And even in the client code itself, abstract the UI from the
business rules.  That is: don't use the _Clicked event to contain your data
access and validation logic.

Finally, if your end-users want GUI, you don't necessarily need to use VB.
Consider tools like DesignBAIS which can give you a browser-based front-end,
all the connectivity is handled for you, there is zero deployment, and the
end-user cost is very inexpensive.  (Contact me for details.)

HTH,
Tony
Nebula R&D
[EMAIL PROTECTED]


djordan wrote:

> I am looking at a scenario of having a VB client with UniObjects
> access a UniVerse database over the internet.  I want to make it as
> simple as possible for the user, ie to be able to do this by just
> launching the VB client on client with internet access.  Has anyone
> done this and what security steps did you take and what issues did
> you have. 
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to