Re: Newbie question



Will,


> Is it safe or smart to ignore the events? That's not a rhetorical
question,
> I really don't know not having done the research because there is no way
I'd
> ever use version 3 of the API in a real application <g>.

If you have a simple single-threaded and single-connection application
without GUI: Yes.
The problem with the Sleep API is that it totally stops Windows
message loop processing and it completetly blocks the application.
There is not problem with that as long as you are sure that there
are no side-effects arising from this.

> I/O. The vast majority of VB "developers" don't even know what an
overlapped
> operation is, never mind that they are central to the way that all of the
NT
> kernels do things.

If you are accessing the COM port directly, don't you need overlapped
I/O as well?

> And this is what scares me. There is always a _huge_ difference between
cute
> little snippets and real applications.

No, the sample was taken from our SMS sending component, which is a bit
more complex, but the connection method is 70% of what I posted. (I stripped
out some additional checks, methods for cancelling, address selection, debug
outputs, etc..) But basically that's it.

> I really don't know not having done the research because there is no way
I'd
> ever use version 3 of the API in a real application <g>.

Why? Probably because you don't know it? Using a COM based API in a
COM oriented development environment is the most natural and easiest
thing you could do. TAPI has a lot of complications, but just making a
simple data connection is really easy, even for a beginner.

OK, if you were talking about TAPI2 and VB I understand your concerns
and I must agree.


Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Ackermannstraße 3
80797 München
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot de
www: www.terasens.de
-------------------------------------


> > There is not much more code needed. You wouldn't even
> > need to process TAPI events for a very simple solution.
>
> Is it safe or smart to ignore the events? That's not a rhetorical
question,
> I really don't know not having done the research because there is no way
I'd
> ever use version 3 of the API in a real application <g>.
>
> And this is what scares me. There is always a _huge_ difference between
cute
> little snippets and real applications. And there is often enough lurking
in
> the dark corners to bite a developer where he sits. For example, there
have
> been several posts here in the past by people who can't understand why all
> of their I/O operations to the COM ports in their TAPI application fail
with
> ERROR_INVALID_PARAMETER (87) even though all of the parameters look fine.
> You and I know that that is because TAPI opens the device for overlapped
> I/O. The vast majority of VB "developers" don't even know what an
overlapped
> operation is, never mind that they are central to the way that all of the
NT
> kernels do things.
>
> No matter, that's why they choose VB, so they can ignore most of the
> details. ;-) In their place, for data communications, I remain convinced
> that it is best to ignore TAPI too, and go straight to the device.
>
> Regards,
> Will
>
>
>


.



Relevant Pages

  • Re: Using TAPI 3.x with .NET
    ... learn some kind of new API and you still don't know what is really ... This TAPI3.NET library is very close to the original TAPI3 API, ... So I can only encourage anyone who wants to do TAPI on .NET to have ... TERASENS GmbH ...
    (microsoft.public.win32.programmer.tapi)
  • Re: Is there an Alternative to TAPI?
    ... just for completeness will mention some other competing telephony ... I have only worked with it on Avaya platform and some people ... program to their API and you then can only work with their platform. ... there is much more development going on than with TAPI. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: LINE_APPNEWCALL vs LINECALLSTATE_OFFERING
    ... Be aware that you will NOT receive APPNEWCALL events for calls created ... with call creating TAPI requests like lineMakeCall, lineUnpark, etc. ... >> Older applications (that negotiated an API version earlier than ...
    (microsoft.public.win32.programmer.tapi)
  • Re: Record Message
    ... TAPI is just an API. ... use some kind of programming language to make those API calls. ... I meant to write "answer the call with TAPI v2". ... jack to the input on the modem, then a line from the output of the modem ...
    (microsoft.public.win32.programmer.tapi)
  • Re: monkeypatch-0.1.2 (alpha)
    ... Besides the issues you mention (new API and adoption), ... Raising an error on a method redefinition is too much. ... is a fairly safe bet for more specialized extensions. ...
    (comp.lang.ruby)

Loading