You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by "David C. Hicks" <dh...@machturtle.com> on 2000/11/17 18:30:19 UTC
SOAP and TCP
Are there any plans to support TCP-based SOAP services in SOAP-J? We
would like to be able to have clients register for notifications and
then the service could "push" SOAP messages to the client when their
requested events occurred. This would require a more permanent kind of
connection rather than the HTTP or SMTP methods available today.
Thanks
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
Re: SOAP and TCP
Posted by "David C. Hicks" <dh...@machturtle.com>.
I don't think that using TCP will keep SOAP from properly marshalling
data. The same mechanisms for transferring data between the client and
the server will still exist, but the roles will be reversed. I just
would like to be able to create a connection and maintain it...or at the
very least let the "client" pretend to be a server long enough to
receive notification.
"Michael T. Huang" wrote:
>
> Hi David
>
> I think that a TCP-based SOAP will lose many features of Java or other object
> systems, for example marshaling pointers to objects , because at present time
> SOAP is "simple"; But I anticipate that XML can be used widely to marshale any
> object communicating info uniformly among different systems.
>
> How do you think?
>
> Michael T. Huang
> fountain
>
> ----- Original Message -----
> From: "David C. Hicks" <dh...@machturtle.com>
> To: "soap dev" <so...@xml.apache.org>
> Sent: Saturday, November 18, 2000 1:30 AM
> Subject: SOAP and TCP
>
> Are there any plans to support TCP-based SOAP services in SOAP-J? We
> would like to be able to have clients register for notifications and
> then the service could "push" SOAP messages to the client when their
> requested events occurred. This would require a more permanent kind of
> connection rather than the HTTP or SMTP methods available today.
>
> Thanks
>
> --
> David C. Hicks
> Mach Turtle Technologies, Inc. (www.machturtle.com)
> dhicks@machturtle.com
> 770-753-8810
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
Re: SOAP and TCP
Posted by "David C. Hicks" <dh...@machturtle.com>.
I don't think that using TCP will keep SOAP from properly marshalling
data. The same mechanisms for transferring data between the client and
the server will still exist, but the roles will be reversed. I just
would like to be able to create a connection and maintain it...or at the
very least let the "client" pretend to be a server long enough to
receive notification.
"Michael T. Huang" wrote:
>
> Hi David
>
> I think that a TCP-based SOAP will lose many features of Java or other object
> systems, for example marshaling pointers to objects , because at present time
> SOAP is "simple"; But I anticipate that XML can be used widely to marshale any
> object communicating info uniformly among different systems.
>
> How do you think?
>
> Michael T. Huang
> fountain
>
> ----- Original Message -----
> From: "David C. Hicks" <dh...@machturtle.com>
> To: "soap dev" <so...@xml.apache.org>
> Sent: Saturday, November 18, 2000 1:30 AM
> Subject: SOAP and TCP
>
> Are there any plans to support TCP-based SOAP services in SOAP-J? We
> would like to be able to have clients register for notifications and
> then the service could "push" SOAP messages to the client when their
> requested events occurred. This would require a more permanent kind of
> connection rather than the HTTP or SMTP methods available today.
>
> Thanks
>
> --
> David C. Hicks
> Mach Turtle Technologies, Inc. (www.machturtle.com)
> dhicks@machturtle.com
> 770-753-8810
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
Re: SOAP and TCP
Posted by "Michael T. Huang" <mi...@sohu.com>.
Hi David
I think that a TCP-based SOAP will lose many features of Java or other object
systems, for example marshaling pointers to objects , because at present time
SOAP is "simple"; But I anticipate that XML can be used widely to marshale any
object communicating info uniformly among different systems.
How do you think?
Michael T. Huang
fountain
----- Original Message -----
From: "David C. Hicks" <dh...@machturtle.com>
To: "soap dev" <so...@xml.apache.org>
Sent: Saturday, November 18, 2000 1:30 AM
Subject: SOAP and TCP
Are there any plans to support TCP-based SOAP services in SOAP-J? We
would like to be able to have clients register for notifications and
then the service could "push" SOAP messages to the client when their
requested events occurred. This would require a more permanent kind of
connection rather than the HTTP or SMTP methods available today.
Thanks
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
Re: SOAP and TCP
Posted by "Michael T. Huang" <mi...@sohu.com>.
Hi David
I think that a TCP-based SOAP will lose many features of Java or other object
systems, for example marshaling pointers to objects , because at present time
SOAP is "simple"; But I anticipate that XML can be used widely to marshale any
object communicating info uniformly among different systems.
How do you think?
Michael T. Huang
fountain
----- Original Message -----
From: "David C. Hicks" <dh...@machturtle.com>
To: "soap dev" <so...@xml.apache.org>
Sent: Saturday, November 18, 2000 1:30 AM
Subject: SOAP and TCP
Are there any plans to support TCP-based SOAP services in SOAP-J? We
would like to be able to have clients register for notifications and
then the service could "push" SOAP messages to the client when their
requested events occurred. This would require a more permanent kind of
connection rather than the HTTP or SMTP methods available today.
Thanks
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810