om]
On Behalf Of Ben Scott
Sent: Tuesday, 5 February 2013 2:41 PM
To: ozDotNet
Subject: Re: SPAM-LOW Re: WCF service best practises
I had the idea that `CreateInstanceAndUnwrap` and `MarshalByRef` used
remoting under the covers, any marshalled objects needed to stick to what
remoting supports.
zdotnet.com] *On Behalf Of *Ben Scott
> *Sent:* Tuesday, 5 February 2013 12:02 PM
>
> *To:* ozDotNet
> *Subject:* Re: SPAM-LOW Re: WCF service best practises
>
> ** **
>
> In the MarkPad Code52 project I was using remoting to implement appdomains
> for plugins, s
et
Subject: Re: SPAM-LOW Re: WCF service best practises
In the MarkPad Code52 project I was using remoting to implement appdomains
for plugins, so that plugins couldn't crash the editor. It didn't work,
probably due to my inexperience, but it seemed like remoting is still the
status q
**
>
> ** **
>
> ** **
>
> **- **Glav
>
> ** **
>
> ** **
>
> ** **
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Katherine Moss
> *Sent:* Monday, 4 February 2013 5:11 PM
> *To:* ozDo
x27;ozDotNet'
Subject: RE: SPAM-LOW Re: WCF service best practises
Nope. Remoting is a way to marshal objects across a boundary whether that be
appDomain (2 separate appDomains on the same machine) or a network boundary
(machine 1 to machine 2). It looks and operates very much like DCOM if
ure others can highlight for you.
- Glav
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Katherine Moss
Sent: Monday, 4 February 2013 5:11 PM
To: ozDotNet
Subject: RE: SPAM-LOW Re: WCF service best practises
Now, remi
Now, remind me. Is System.Net.EnterpriseServices the same as
System.NET.Remoting?
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Sunday, February 03, 2013 5:21 PM
To: ozDotNet
Subject: Re: SPAM-LOW Re: WCF service best practises
On Sat, Feb 2, 2013 at 2:09 PM, Paul Glavich wrote:
> At the risk of being argumentative, we asked for this. Maybe not you or me
> specifically, but the community at large has. I agree the number of
> technologies at play, particularly in this space is large but it makes it
> all the more **intere
Apparently the .NET remoting documentation has been removed and you have to
hunt around in the archives for it now (I haven't looked myself), so that's
probably a hint about being out-of-date. However, I have a sentimental
feeling for remoting as we have an intensely used client-server app out
ther
5:25 AM
To: ozDotNet
Subject: RE: SPAM-LOW Re: WCF service best practises
I thought that .net remoting is kind of out-of-date and shouldn't be used
because of all of the new technologies. Or is it out-of-date? And now
you're making me question my plans for my first Open Source project th
Glavich
Sent: Friday, February 01, 2013 10:10 PM
To: 'ozDotNet'
Subject: RE: SPAM-LOW Re: WCF service best practises
At the risk of being argumentative, we asked for this. Maybe not you or me
specifically, but the community at large has. I agree the number of
technologies at play, pa
phen Price
Sent: Saturday, 2 February 2013 11:52 AM
To: ozDotNet
Subject: Re: SPAM-LOW Re: WCF service best practises
I must be getting old too Greg. Your rants are starting to make sense. I'm
even nodding my head as I read.
I've said it before, they invent this stuff faster than
f Of David Connors
Sent: Saturday, 2 February 2013 9:28 AM
To: ozDotNet
Subject: Re: SPAM-LOW Re: WCF service best practises
On Fri, Feb 1, 2013 at 7:44 PM, Paul Glavich mailto:subscripti...@theglavs.com> > wrote:
Webapi is a reaction to attitudes as described below.
[ ... ]
...@ozdotnet.com]
On Behalf Of Davy Jones
Sent: Friday, 1 February 2013 9:49 PM
To: ozDotNet
Subject: Re: SPAM-LOW Re: WCF service best practises
I must be getting old.
XML-rpc (simple XML http)
XML-soap complex ish
Wcf. Really complex
Rest/Jason complex ish
Web API simple
A full turn of the
I must be getting old too Greg. Your rants are starting to make sense. I'm
even nodding my head as I read.
I've said it before, they invent this stuff faster than anyone can learn
it. Lets hope its heading in the right direction. For the children's sake.
On Sat, Feb 2, 2013 at 7:15 AM, Greg Keog
Folks, I'm pleased to see that other people here are irritated by the
number of choices we have for communication and by the complexity of WCF. I
was also pleased to see someone else was bewlidered by having WebAPI buried
inside MVC and found a way of starting with a managable skeleton project.
Lu
On Fri, Feb 1, 2013 at 7:44 PM, Paul Glavich wrote:
> Webapi is a reaction to attitudes as described below.
>
>
[ ... ]
> Ofcourse WCF can do REST too, you just have to twiddle a few hundred
> different knobs on the right way. I would argue WCF is not bullshit. WCF
> comprises way more than
m] On
Behalf Of Davy Jones
Sent: Friday, February 01, 2013 5:49 AM
To: ozDotNet
Subject: Re: SPAM-LOW Re: WCF service best practises
I must be getting old.
XML-rpc (simple XML http)
XML-soap complex ish
Wcf. Really complex
Rest/Jason complex ish
Web API simple
A full turn of the wheel in 12 year
bject:* SPAM-LOW Re: WCF service best practises
On Fri, Feb 1, 2013 at 7:23 AM, Craig van Nieuwkerk
wrote:
ASP.NET WebAPI seems to be the new hotness. I don't have much experience
with WCF, but everyone I talk to says it is too heavy and complicated.
WebAPI tries to simplify things.
development life continues...
- Glav
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of David Connors
Sent: Friday, 1 February 2013 9:10 AM
To: ozDotNet
Subject: SPAM-LOW Re: WCF service best practises
On Fri, Feb 1, 2013 at 7:23 AM
I'd be interested in hearing any experiences of those using ServiceStack.
It seems like a great platform - anyone care to share their experiences
with it?
Cheers
Grant
On 1 February 2013 08:28, William Luu wrote:
> Also have a look into servicestack.net
>
> http://www.servicestack.net/mythz_b
On Fri, Feb 1, 2013 at 7:23 AM, Craig van Nieuwkerk wrote:
> ASP.NET WebAPI seems to be the new hotness. I don't have much experience
> with WCF, but everyone I talk to says it is too heavy and complicated.
> WebAPI tries to simplify things.
WCF is a bunch of bullshit. People who use it just do
http://xkcd.com/927/
Cheers
Ken
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Friday, 1 February 2013 8:53 AM
To: ozDotNet
Subject: Re: WCF service best practises
They've been flogging WebAPI in recent MSDN magazines, but I go
They've been flogging WebAPI in recent MSDN magazines, but I got the
impression that it's just REST more formalised with contracts.
Perhaps this makes sense from the hints I've been reading. WCF is heavy and
complicated and over-engineered to be general purpose (which is fine and
I've benefited fr
t;
Subject: Re: WCF service best practises
ASP.NET WebAPI seems to be the new hotness. I don't have much experience
with WCF, but everyone I talk to says it is too heavy and complicated.
WebAPI tries to simplify things.
On Fri, Feb 1, 2013 at 7:50 AM, Greg Keogh wrote:
What
ASP.NET WebAPI seems to be the new hotness. I don't have much experience
with WCF, but everyone I talk to says it is too heavy and complicated.
WebAPI tries to simplify things.
On Fri, Feb 1, 2013 at 7:50 AM, Greg Keogh wrote:
> What about the death of WCF as everything else in the modern
>>
>
> What about the death of WCF as everything else in the modern technological
> landscape seems to be dying? Is WCF another one?
>
Everything that dies has to be replaced in some form or another. If WCF is
dying, what's its replacement?
If I want to publicly expose my .NET "service" over the wi
[mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Wednesday, January 30, 2013 5:08 PM
To: ozDotNet
Subject: WCF service best practises
Folks, I have created the stub of a WCF service that I've sanity checked is
working okay when hosted in IIS, Azure, a Windows Service and even the co
Folks, I have created the stub of a WCF service that I've sanity checked is
working okay when hosted in IIS, Azure, a Windows Service and even the
command promt. It will be consumed by desktop apps and Silverlight. The
initial code came out of the VS2012 new project template and I just started
addi
29 matches
Mail list logo
