Claus,
Has anyone on the list tried to build a really huge application withI've written a massive (in terms of complexity, not size) Delphi App which works with UniVerse and UniData.
delphi/vb??,
and if so, what approach did you use to make it easy to be several developers to work on the application at the same time?? I understand that if i build my app. around a central small executable and a lot of dll's then several developers can work on their own subprojects on a single dll, but how do you maintain connection to u2, as the dll functions cant see the unisession object in the central executable ?
We approached it from a component standpoint and let individual developers 'own' their share of components. AVOID .dll files wherever possible. Components compile into the final project and therefore cannot get overwritten or misfiled on the client;s machine. I use .dll (or the linux .so) files only as a last resort. They make for more tech support tahn internal components.
what is best to reduce licensing ?? - using some sort of a broker to keep
connection to u2 ?
Make your App a Client/Server model, with the Server having a UniObjects connection to the database. You can manange the license usage from a central point.
--
- Charles Barouch
(718) 762-3884 x 1 - Key Ally Voice Mail
cbarouch - Skype (Free VoIP Phone) [EMAIL PROTECTED] - Consulting services
[EMAIL PROTECTED] - News
[EMAIL PROTECTED] - U2-Users Moderator [EMAIL PROTECTED] - Zeus Data Integration
Mount Olympus, Home of Zeus Data Integration
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
