Subject Re: [IB-Architect] SOME SOLUTIONS TO OLD PROBLEMS
Author Marcelo Lopez Ruiz
Bot-side questions:
What other bots are you running? What tools did you use to build them? How
cross-platform are they? What's the ISALIVE bot about - an IB-ping bot, I
presume? How do bots react to unavaliable servers - mails, paging, file
system logging, logging to local IB, logging to system log on NT?

<SNIP>
"The GDBCONTROL daemon not only is connected to a core gdb, it keeps in
contact
with a user interface with via UDP broadcasts that can also log all
connection
activity. The actual daemon has no interface."
</SNIP>
You lost me here.


Client-side questions:
How do your clients manage their connections to the database? Do you keep
active transactions while they browse data, or do they do this in a
disconnected fashion?

Server-side questions:
Uhh... I'm too drowsy right now. See you all tomorrow.

I'd like to have a tutorial before building wizards for this. So people can
build a sample system themselves, following a step-by-step guide which
explains the reasons behind the actions, and then use a wizard to build the
stock stuff quickly.

Marcelo Lopez Ruiz

P.S.: COMMENTS, QUESTIONS, INSULTS. If you need more, just ask, I'm at your
service :-)

Good night, Claudio (at least *you* are in my time zone!)


-----Original Message-----
From: dcalford <dcalford@...>
To: IB-Architect@egroups.com <IB-Architect@egroups.com>
Date: Wednesday, June 21, 2000 12:22 AM
Subject: Re: [IB-Architect] SOME SOLUTIONS TO OLD PROBLEMS


>Ok,
>
>Since I have had such a good response from people who want me to continue,
I
>will try my best to get the rest of the operational methods I have posted
as
>quickly as time allows.
>
>What I ask is, PLEASE POST COMMENTS, QUESTIONS, INSULTS, you name it, I
want
>to hear it. What I am posting is over 5 years of experience and problem
>solving combined with a year of intense application. I need all the
proding I
>can get to not only put forward the solutions, but also to put forward the
>dead end paths that were taken and why they failed. I am also trying to
>explain some approaches that are not intuitive to those who have not had
the
>same development cycles as I have had.
>
>On another note, all the different items I am explaining here, although it
>sounds complex, is actually quite simple to use and implement. (no one
wants a
>system that you need a full time staff to maintain). Even a small
>application can be designed to use these methods to it's benefit. I will
do
>my best to put my own code up with extensive examples. I will assist
anyone
>who wants to build a few wizards for the implementation. So, even though
you
>think your app does not need this kind of design, please, review the code
and
>see if you can put the time in to create a series of small tools that will
>help the community in general. The person you may be helping could be
>yourself.....
>
>Best regards
>
>Dalton