Hi Dan
On 01/08/13 22:51, Daniel Kulp wrote:
On Aug 1, 2013, at 4:58 PM, Sergey Beryozkin wrote:
Hi Dan
On 31/07/13 23:42, Daniel Kulp wrote:
On Jul 30, 2013, at 12:07 PM, Sergey Beryozkin wrote:
I'd rather go and enable the direct dispatch style by default, will make things
a bit simpl
On Aug 1, 2013, at 4:58 PM, Sergey Beryozkin wrote:
> Hi Dan
> On 31/07/13 23:42, Daniel Kulp wrote:
>>
>> On Jul 30, 2013, at 12:07 PM, Sergey Beryozkin wrote:
>>
>>> I'd rather go and enable the direct dispatch style by default, will make
>>> things a bit simpler for users (no need to know
Hi Dan
On 31/07/13 23:42, Daniel Kulp wrote:
On Jul 30, 2013, at 12:07 PM, Sergey Beryozkin wrote:
Hi Dan, others
Do you remember why LocalConduit uses a piped-style communication by default ?
The problem with that it causes calls with empty payloads hang (plenty of cases
with RS but also
On Jul 30, 2013, at 12:07 PM, Sergey Beryozkin wrote:
> Hi Dan, others
>
> Do you remember why LocalConduit uses a piped-style communication by default
> ? The problem with that it causes calls with empty payloads hang (plenty of
> cases with RS but also possible with SOAP GET for ex), unless
+1 for using Direct Dispatch by default.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye
Hi Dan, others
Do you remember why LocalConduit uses a piped-style communication by
default ? The problem with that it causes calls with empty payloads hang
(plenty of cases with RS but also possible with SOAP GET for ex), unless
users go and enable a direct dispatch style.
I'd rather go and
