Hey I didn't really say it was M$'s fault either ;)
You're spot on about leveraging other libraries, using cfobject etc.
But in a way, that's just what Java and .net solutions are doing too.
If you want all the extra WS features you're not going to achieve it
easily in any language (guess)... Exc
FYI: Starting eSeminar in 5 minutes.
Begin forwarded message:
> From: Robin Hilliard
> Date: 12 December 2008 7:36:35 AM
> To: cfaussie@googlegroups.com
> Subject: Fwd: Adobe ColdFusion Interface eSeminar
>
> Just a reminder that I'll be giving an Adobe eSeminar on CFInterface
> online at 2 pm
2008/12/11 Michal :
>
> I need to gather information about CF and web services. Could anybody
> point me to some resources about best practices when implementing web
> services in CF? Any lessons learned, gotchas from your own experience
> are even better.
It's not quite clear to whether you're w
> Kai, you sort of say that CF doesn't support WS-* but could that might
> be writing it off too early.
>
> In the Java world, is it axis (only) that provides those features? I
> think it takes more than that right? Should we expect so much from CF?
>
It's not only Axis, but Axis is a common way o
Kai, you sort of say that CF doesn't support WS-* but could that might
be writing it off too early.
In the Java world, is it axis (only) that provides those features? I
think it takes more than that right? Should we expect so much from CF?
On the publishing side there's flexability to handcraft
Just a reminder that I'll be giving an Adobe eSeminar on CFInterface
online at 2 pm Australian EST today.
Cheers,
Robin
Begin forwarded message:
> From: Robin Hilliard
> Date: 9 December 2008 10:10:54 AM
> To: cfaussie@googlegroups.com
> Subject: Adobe ColdFusion Interface eSeminar
>
> Meetin
Barry,
>
>> REST is not just the flavor of the month in web 2.0 companies it's
>> actually
>> a very good way of doing things.
>
> except if that's not an option, and all you're left with is a bunch of
> webservices, especially if they're .NET webservices requiring security
> credentials and tok
> REST is not just the flavor of the month in web 2.0 companies it's actually
> a very good way of doing things.
except if that's not an option, and all you're left with is a bunch of
webservices, especially if they're .NET webservices requiring security
credentials and tokens, rah, rah.
> To ge
I like REST, it's basically what we have always been doing prior to SOAP
except u return structured data rather than HTML
it's lightweight and efficient.. where as SOAP is rather heavy!
as for the whole SEO type url parameters with REST, I'm not really so
fussed whether its
http://localhost/ind
Hi guys,
Rae's link basically just describes security on the HTTP level and
using some
of the role-based security and CFLOGIN in CF. That's fine, but quite
often
unfortunately your communication partners expect you to support
particular
technologies and standards in the WS world.
When it co
10 matches
Mail list logo
