On 6/13/06, Nathan Mittler [EMAIL PROTECTED] wrote:
So it sounds like we're all in agreement on the content-type header. For
text, it would be something like text
There could be a few values of Content-type which map to text
(text/xml, application/soap, application/xml etc).
Incidentally the
On 6/14/06, Brian McCallister [EMAIL PROTECTED] wrote:
On Jun 13, 2006, at 3:06 PM, Nathan Mittler wrote:
So it sounds like we're all in agreement on the content-type
header. For
text, it would be something like text and for bytes it would be
application/octet-stream. So this would not be
On 6/14/06, Mittler, Nathan [EMAIL PROTECTED] wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram
Chirino
Sent: Wednesday, June 14, 2006 12:40 PM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
On 6/14/06, Brian
On 6/14/06, Mittler, Nathan [EMAIL PROTECTED] wrote:
For map messages, on the c++ side of things we would essentially have to
write a schema file for the layout of a map message. The c++ stomp
client would have to be coded against that schema to properly parse the
message. Unfortunately, we
Excellent! I'm breathing a sigh of relief :)
-Original Message-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 8:55 AM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
On 6/14/06, Mittler, Nathan [EMAIL PROTECTED] wrote:
For map
On Jun 13, 2006, at 3:06 PM, Nathan Mittler wrote:
So it sounds like we're all in agreement on the content-type
header. For
text, it would be something like text and for bytes it would be
application/octet-stream. So this would not be an application-level
header, but would be used by my
On Jun 14, 2006, at 10:21 AM, Mittler, Nathan wrote:
Ok, so application-level is referring to the C++ library, not the user
of the library? If so that eliminates the need for another header
like
amq-msg-type.
We still want the transform header for the stomp adaptor though, in
order to
On 6/14/06, Hiram Chirino [EMAIL PROTECTED] wrote:
On 6/14/06, Nathan Mittler [EMAIL PROTECTED] wrote:
A whiteboard would be really handy ... you guys aren't in NY by any
chance,
are you? ;)
DOH I was just there last week (for 3 hours)! Want to visit Tampa
Florida?
HA ... give me a call
On 6/14/06, Nathan Mittler [EMAIL PROTECTED] wrote:
On 6/14/06, Hiram Chirino [EMAIL PROTECTED] wrote:
On 6/14/06, Nathan Mittler [EMAIL PROTECTED] wrote:
A whiteboard would be really handy ... you guys aren't in NY by any
chance,
are you? ;)
DOH I was just there last week (for 3
I think that clears things up for me a bit - what you're proposing makes
sense. I'll poke around today and see what I can come up with.
Thanks,
Nate
On 6/12/06, Brian McCallister [EMAIL PROTECTED] wrote:
On Jun 12, 2006, at 4:14 PM, Nathan Mittler wrote:
Agreed ... using the type header is
FWIW I'd like to have content-type header support. Couldn't we then
use content-type as the standard header that any Stomp-JMS bridge
would use to decide if something is a TextMessage or a BytesMessage?
On 6/13/06, Nathan Mittler [EMAIL PROTECTED] wrote:
I think that clears things up for me a
to
be working.
2) step back and create a pluggable framework.
Regards,
Nate
-Original Message-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 10:57 AM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
FWIW I'd like to have content
Sounds good to me.
+1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram
Chirino
Sent: Tuesday, June 13, 2006 1:45 PM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
On 6/13/06, Mittler, Nathan [EMAIL PROTECTED] wrote:
Just
I would suggest that we use a weak form of specification encoding.
ActiveMQ already uses pseudo-urls in a lot of places, and named
transforms trump class names, usually:
yeah! URI style configuration rocks!
-Brian
--
Regards,
Hiram
So it sounds like we're all in agreement on the content-type header. For
text, it would be something like text and for bytes it would be
application/octet-stream. So this would not be an application-level
header, but would be used by my stomp client code to determine which message
type to
PROTECTED]
Sent: Tuesday, June 13, 2006 10:57 AM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
FWIW I'd like to have content-type header support. Couldn't we then
use content-type as the standard header that any Stomp-JMS bridge
would use to decide if something
-
From: Brian McCallister [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 12:20 PM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
On Jun 13, 2006, at 8:11 AM, Mittler, Nathan wrote:
James,
I think that's what we're proposing here. I proposed amq-msg-type,
but I
: Tuesday, June 13, 2006 10:57 AM
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP and JMSType
FWIW I'd like to have content-type header support. Couldn't we then
use content-type as the standard header that any Stomp-JMS bridge
would use to decide if something is a TextMessage
@geronimo.apache.org
Subject: Re: STOMP and JMSType
On Jun 13, 2006, at 8:11 AM, Mittler, Nathan wrote:
James,
I think that's what we're proposing here. I proposed amq-msg-type,
but I suppose content-type is just as good. I think Brian's main
concern (Brian, correct me if I'm wrong) is that he'd like
On 6/13/06, Brian McCallister [EMAIL PROTECTED] wrote:
On Jun 13, 2006, at 10:36 AM, Hiram Chirino wrote:
The think your views are a bit STOMP point of view centric. bytes
messages work fine when both end assume you are just moving around
bytes messages.. and it's true everything can
Could you guys point me to a place in AMQ where this sort of thing is being
done? That would save me a lot of searching =)
I'm viewing this problem from the client side - the Stomp C++ client that
Tim Bish and I are writing currently supports text and bytes messages. So
when I get a stomp
On Jun 13, 2006, at 1:50 PM, Nathan Mittler wrote:
Could you guys point me to a place in AMQ where this sort of thing
is being
done? That would save me a lot of searching =)
I'm viewing this problem from the client side - the Stomp C++
client that
Tim Bish and I are writing currently
On 6/13/06, Nathan Mittler [EMAIL PROTECTED] wrote:
Could you guys point me to a place in AMQ where this sort of thing is being
done? That would save me a lot of searching =)
Its not really done anywhere else :-(
I'm viewing this problem from the client side - the Stomp C++ client that
Tim
JMSType is a reserved header in JMS, for use at the application
level. I think what you are proposing is more accurately an ActiveMQ
specific transform header. I think this type of transform should
either be a real, arbitrary, pluggable, transform mechanism, or
should not be done.
I
On Jun 12, 2006, at 4:14 PM, Nathan Mittler wrote:
Agreed ... using the type header is not an option.
--- From the bug report ---
It isn't possible to reuse the type header (JMSType) for the
purpose of sending through the information as to what type of message
it is (text or bytes). So
25 matches
Mail list logo
