[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866530#action_12866530
]
Cliff Jansen commented on QPID-2589:
Would it be possible to build the WCF (channel and
Perhaps it would be useful for somebody to assist this debate by
introducing the messaging API in the .NET context and addressing why,
for example, .NET programmers need this API, but Java programmers
don't. Or why a developer who might be inclined to use WCF should use
this messaging API
[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866533#action_12866533
]
Gordon Sim commented on QPID-2589:
--
The major outages are dtx support and message body
Hi Josh,
Thx for your reply. Iam not an expert with the SELinux API, I
have looked at it before. I chose that because it sounded familiar and I
thot it would be easy to start with. If you can suggest anything better for
me, that will be great.
Thanks
Kanthi.
--
View this message
Hi Josh,
Thx for your reply. Iam not an expert with the SELinux API, I
have looked at it before. I chose that because it sounded familiar and I
thot it would be easy to start with. If you can suggest anything better for
me, that will be great.
Thanks
Kanthi.
--
View this message
Gordon Sim wrote:
On 05/10/2010 09:33 PM, tr...@apache.org wrote:
Author: tross
Date: Mon May 10 20:33:19 2010
New Revision: 942892
URL: http://svn.apache.org/viewvc?rev=942892view=rev
Log:
QPID-2589 - Applied patch from Chuck Rolke.
This commit adds a new component and yet another approach
Cliff Jansen wrote:
Perhaps it would be useful for somebody to assist this debate by
introducing the messaging API in the .NET context and addressing why,
for example, .NET programmers need this API, but Java programmers
don't. Or why a developer who might be inclined to use WCF should use
this
On 05/12/2010 11:21 AM, Cliff Jansen wrote:
Perhaps it would be useful for somebody to assist this debate by
introducing the messaging API in the .NET context and addressing why,
for example, .NET programmers need this API, but Java programmers
don't. Or why a developer who might be inclined to
cmake configure step broken Tues night 11-April
---
Key: QPID-2601
URL: https://issues.apache.org/jira/browse/QPID-2601
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client
Gordon Sim wrote:
On 05/12/2010 11:21 AM, Cliff Jansen wrote:
Perhaps it would be useful for somebody to assist this debate by
introducing the messaging API in the .NET context and addressing why,
for example, .NET programmers need this API, but Java programmers
don't. Or why a developer who
On 05/12/2010 12:50 PM, Rafael Schloming wrote:
Even if there isn't interest in using this API directly, I think there
is huge benefit to having all the clients share a common architecture as
much as possible. Since the purpose of the messaging API is really to
expose all the features of AMQP
[
https://issues.apache.org/jira/browse/QPID-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866556#action_12866556
]
Andrew Kennedy commented on QPID-2600:
--
I have also based the Java group entity parsing
[
https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866562#action_12866562
]
Andrew Kennedy commented on QPID-2541:
--
Understood, and this is what I would like - If
[
https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866573#action_12866573
]
Rajith Attapattu commented on QPID-2541:
Thanks for the explanation.
As long as the
[
https://issues.apache.org/jira/browse/QPID-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866580#action_12866580
]
Rajith Attapattu commented on QPID-2600:
Thx good catch !
user =
[
https://issues.apache.org/jira/browse/QPID-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866586#action_12866586
]
Rajith Attapattu commented on QPID-2600:
However currently the c++ broker doesn't
On 05/10/2010 10:21 AM, Rajith Attapattu wrote:
I am hoping to do as many static pages as I can during the weekend.
However I'd appreciate if people can volunteer to help with some of
the static pages.
The first step might be to take inventory of what gets handled as static
HTML. I hope that
Thx for your reply. Iam not an expert with the SELinux API, I
have looked at it before. I chose that because it sounded familiar and I
thot it would be easy to start with. If you can suggest anything better for
I'm actually looking at this again - the trick is understanding
On Wed, May 12, 2010 at 10:43 AM, Jonathan Robie
jonathan.ro...@redhat.com wrote:
On 05/10/2010 10:21 AM, Rajith Attapattu wrote:
I am hoping to do as many static pages as I can during the weekend.
However I'd appreciate if people can volunteer to help with some of
the static pages.
The
On 05/12/2010 10:53 AM, Rajith Attapattu wrote:
On Wed, May 12, 2010 at 10:43 AM, Jonathan Robie
jonathan.ro...@redhat.com wrote:
The first step might be to take inventory of what gets handled as static
HTML. I hope that will be relatively few pages, and that it will not include
the
[
https://issues.apache.org/jira/browse/QPID-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston closed QPID-2601.
--
Assignee: Steve Huston
Resolution: Cannot Reproduce
Problem was apparently the result of
21 matches
Mail list logo
