>
> > To me, it seems the missing piece is the ability to
> > invoke CFML from other sources than an HTTP request.
>
> I agree - and Ben Forta's tour report mentioned the ability to access
> CFCs from Java. My reading of that is that such functionality would be
> separate from the event gateway (but I don't have insight into the
> product team's features so I may be off-base). It seems to me that the
> ability to access CFCs from Java is a pre-requisite for event gateways
> and I'd be very surprised if the only way to access CFCs from Java was
> via the event gateway framework!
>
> > While the event gateway
> > will provide that, it seems it will also provide more than that.
>
> Yes, that is my reading of what has been said publicly too.
>
> > The reason I feel that way is
> > because I think it is far too easy for the community and 3rd party
> companies
> > to provide various protocol adapters. With a simple Java API for the
> > invocation of CFML it would be quite easy for someone with Java
> experience
> > to write these adapters.
>
> I hope you're right. I don't see how it could be anything but
> beneficial for CF to have community-developed protocol adapters -
> either through the event gateway or separately. If the community does
> a better job at creating a "gateway" framework than Macromedia, CFers
> will have more choice and the bar will have been raised even further.
> In what way is that a bad thing?
I agree and support the above paragraphs -- the event gateway will
provide an easy way to expand the use of CF to address a larger portion
of the total IT pie & play nicely within the j2ee environment (and take
on a bigger roll).
With the availability of a well-defined event gateway interface, Java
programmers will be able to extend or refine this method of invoking CF
code.
With the availability of a well-defined Java API, Java programmers
should be able to write a portion of their Java applications using CFML
-- this can only benefit both the CF and Java communities.
As an interesting aside, with both of the above, the use wouldn't
necessarily be limited to Java -- other languages/environments could
take advantage of the interface.
Dick
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
