You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Joe Pruitt <j....@f5.com> on 2002/10/18 18:28:02 UTC
RE: SOAP based FTP server , some academic issues, opinions needed
!
SOAP was designed to be transport independent. It's only that most of the implementations support http(s) as the default transport. I do know that with Apache you can create your SOAP call and serialize it to a string to use for your own transport. I'm not sure if they support native sockets but I'd be surprised if they don't. I do know that several of the other packages out there in other languages support SMTP/POP, raw sockets, etc as an option. I think it is completely viable to use any transport mechanism that you require for you application. The only thing you need to worry about is interoperability with other product implementations of either your client or server end of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the design phase of a File Transfer server (similar to FTP) that will implement its protocol through SOAP.What I mean?That the server will exhange protocol commands with its clients through SOAP-XML envelopes. I have to say I quite familiar with XML parsers and Java too.The whole implementation will be in Java.In tha last 2 weeks I am investigating SOAP through books , web resources , etc. Most of the resources I have found ,are dealing with SOAP as part of the Web Services thing!Thats fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server and clients.Imagine that my envelopes will have some FTP like commands.Thats all.I am in the design phase of the protocol itself , and I am bit stuck in way , on how my messages will be travelling through the wire.The thing that worries me about is tha SOAP is almost bound top HTTP.In my case I dont think that I really need HTTP? What do you think about that?My solution is to send SOAP envelopes, through plain socket /stream connections .The other thing that worries me about is that i still dont know if existing JAVA SOAP libraries like APACHE , JAXM can help me deal easily with SOAP messages that are not bind to HTTP wrapper..has anyone tried something like that?So probably using Apache Xerces I have to provide a mechanism for marshalling and demarshalling my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but in my case I dont think is neccesary.I am really trying to find out , if that use of SOAP can be described as message-style SOAP .For those who might ask why SOAP , you can use any custom XML protocol , I shall answer that is the spec and I cant do anything about that.It is going to be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by Paris Apostolopoulos <pa...@freemail.gr>.
Hi Paramdeep Singh, thanks for your reply
Probably I did not describe it correct. I am sorry.
I am trying to implement a file server/client (similar to FTP) for file
download/upload .
The protocol that I have to use is a custom made protocol based on SOAP
messages.
The thing I was mentioning is , whether to have these SOAP messages over
HTTP , or simple on top of plain streams!
And as I had mentioned I am not so sure if the HTTP wrapper in my SOAP
messages would be necessary for my implementation.
Thanks for your time
Papo
-----Original Message-----
From: Paramdeep Singh [mailto:pdsingh@HotPOP.com]
Sent: Monday, October 21, 2002 7:17 AM
To: soap-user@xml.apache.org
Subject: Re: SOAP based FTP server , some academic issues, opinions
needed!
Hi PAPO,
I am not sure, what you are trying to do!
1) Are you trying to implement functionality of FTP on top of SOAP?
2) Or are you trying to implement "passing of SOAP messages" on top of
FTP?
If you are trying to implement (2), then you should look at what Anne is
suggesting. But in case you are trying to do (1), then I am not very
sure if it is the right thing to do. FTP is a binary protocol, which has
many features favouring file transfer. If you try to implement FTP on
top of HTTP, then this might not be very efficient.
In case you are targetting any other transport, then I would question,
why at all are you not happy with FTP?? FTP is a "standard protocol" and
I think is more widely accepted than SOAP! ;)
Warm Regards,
Paramdeep
----- Original Message -----
From: Anne Thomas Manes <ma...@manes.net>
To: soap-user@xml.apache.org
Sent: Friday, October 18, 2002 10:59 PM
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
I suggest that you take a look at Apache Axis
(http://xml.apache.org/axis). It provides a really nice transport
framework that allows you to send and receive SOAP messages over almost
any type of transport. You would also be able to use its serialization
services. Apache Axis is very modular, and you should be able to pick
and choose which parts of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that
made the whole project weird is that I am going to use a very small
functionality provided by the SOAP itself.I should describe my try as a
messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite
academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a
string to use for your own transport. I'm not sure if they support
native sockets but I'd be surprised if they don't. I do know that
several of the other packages out there in other languages support
SMTP/POP, raw sockets, etc as an option. I think it is completely
viable to use any transport mechanism that you require for you
application. The only thing you need to worry about is interoperability
with other product implementations of either your client or server end
of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will
implement its protocol through SOAP.What I mean?That the server will
exhange protocol commands with its clients through SOAP-XML envelopes. I
have to say I quite familiar with XML parsers and Java too.The whole
implementation will be in Java.In tha last 2 weeks I am investigating
SOAP through books , web resources , etc. Most of the resources I have
found ,are dealing with SOAP as part of the Web Services thing!Thats
fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like
commands.Thats all.I am in the design phase of the protocol itself , and
I am bit stuck in way , on how my messages will be travelling through
the wire.The thing that worries me about is tha SOAP is almost bound top
HTTP.In my case I dont think that I really need HTTP? What do you think
about that?My solution is to send SOAP envelopes, through plain socket
/stream connections .The other thing that worries me about is that i
still dont know if existing JAVA SOAP libraries like APACHE , JAXM can
help me deal easily with SOAP messages that are not bind to HTTP
wrapper..has anyone tried something like that?So probably using Apache
Xerces I have to provide a mechanism for marshalling and demarshalling
my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who
might ask why SOAP , you can use any custom XML protocol , I shall
answer that is the spec and I cant do anything about that.It is going to
be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by Paris Apostolopoulos <pa...@freemail.gr>.
Hi Paramdeep Singh, thanks for your reply
Probably I did not describe it correct. I am sorry.
I am trying to implement a file server/client (similar to FTP) for file
download/upload .
The protocol that I have to use is a custom made protocol based on SOAP
messages.
The thing I was mentioning is , whether to have these SOAP messages over
HTTP , or simple on top of plain streams!
And as I had mentioned I am not so sure if the HTTP wrapper in my SOAP
messages would be necessary for my implementation.
Thanks for your time
Papo
-----Original Message-----
From: Paramdeep Singh [mailto:pdsingh@HotPOP.com]
Sent: Monday, October 21, 2002 7:17 AM
To: soap-user@xml.apache.org
Subject: Re: SOAP based FTP server , some academic issues, opinions
needed!
Hi PAPO,
I am not sure, what you are trying to do!
1) Are you trying to implement functionality of FTP on top of SOAP?
2) Or are you trying to implement "passing of SOAP messages" on top of
FTP?
If you are trying to implement (2), then you should look at what Anne is
suggesting. But in case you are trying to do (1), then I am not very
sure if it is the right thing to do. FTP is a binary protocol, which has
many features favouring file transfer. If you try to implement FTP on
top of HTTP, then this might not be very efficient.
In case you are targetting any other transport, then I would question,
why at all are you not happy with FTP?? FTP is a "standard protocol" and
I think is more widely accepted than SOAP! ;)
Warm Regards,
Paramdeep
----- Original Message -----
From: Anne Thomas Manes <ma...@manes.net>
To: soap-user@xml.apache.org
Sent: Friday, October 18, 2002 10:59 PM
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
I suggest that you take a look at Apache Axis
(http://xml.apache.org/axis). It provides a really nice transport
framework that allows you to send and receive SOAP messages over almost
any type of transport. You would also be able to use its serialization
services. Apache Axis is very modular, and you should be able to pick
and choose which parts of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that
made the whole project weird is that I am going to use a very small
functionality provided by the SOAP itself.I should describe my try as a
messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite
academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a
string to use for your own transport. I'm not sure if they support
native sockets but I'd be surprised if they don't. I do know that
several of the other packages out there in other languages support
SMTP/POP, raw sockets, etc as an option. I think it is completely
viable to use any transport mechanism that you require for you
application. The only thing you need to worry about is interoperability
with other product implementations of either your client or server end
of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will
implement its protocol through SOAP.What I mean?That the server will
exhange protocol commands with its clients through SOAP-XML envelopes. I
have to say I quite familiar with XML parsers and Java too.The whole
implementation will be in Java.In tha last 2 weeks I am investigating
SOAP through books , web resources , etc. Most of the resources I have
found ,are dealing with SOAP as part of the Web Services thing!Thats
fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like
commands.Thats all.I am in the design phase of the protocol itself , and
I am bit stuck in way , on how my messages will be travelling through
the wire.The thing that worries me about is tha SOAP is almost bound top
HTTP.In my case I dont think that I really need HTTP? What do you think
about that?My solution is to send SOAP envelopes, through plain socket
/stream connections .The other thing that worries me about is that i
still dont know if existing JAVA SOAP libraries like APACHE , JAXM can
help me deal easily with SOAP messages that are not bind to HTTP
wrapper..has anyone tried something like that?So probably using Apache
Xerces I have to provide a mechanism for marshalling and demarshalling
my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who
might ask why SOAP , you can use any custom XML protocol , I shall
answer that is the spec and I cant do anything about that.It is going to
be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: SOAP based FTP server , some academic issues, opinions needed!
Posted by Paramdeep Singh <pd...@HotPOP.com>.
MessageHi PAPO,
I am not sure, what you are trying to do!
1) Are you trying to implement functionality of FTP on top of SOAP?
2) Or are you trying to implement "passing of SOAP messages" on top of FTP?
If you are trying to implement (2), then you should look at what Anne is suggesting. But in case you are trying to do (1), then I am not very sure if it is the right thing to do. FTP is a binary protocol, which has many features favouring file transfer. If you try to implement FTP on top of HTTP, then this might not be very efficient.
In case you are targetting any other transport, then I would question, why at all are you not happy with FTP?? FTP is a "standard protocol" and I think is more widely accepted than SOAP! ;)
Warm Regards,
Paramdeep
----- Original Message -----
From: Anne Thomas Manes
To: soap-user@xml.apache.org
Sent: Friday, October 18, 2002 10:59 PM
Subject: RE: SOAP based FTP server , some academic issues, opinions needed!
I suggest that you take a look at Apache Axis (http://xml.apache.org/axis). It provides a really nice transport framework that allows you to send and receive SOAP messages over almost any type of transport. You would also be able to use its serialization services. Apache Axis is very modular, and you should be able to pick and choose which parts of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that made the whole project weird is that I am going to use a very small functionality provided by the SOAP itself.I should describe my try as a messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for my (academic) implementation , might be totally out of the standar and famous way that SOAP is being used now.But that I think is a quite academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions needed!
SOAP was designed to be transport independent. It's only that most of the implementations support http(s) as the default transport. I do know that with Apache you can create your SOAP call and serialize it to a string to use for your own transport. I'm not sure if they support native sockets but I'd be surprised if they don't. I do know that several of the other packages out there in other languages support SMTP/POP, raw sockets, etc as an option. I think it is completely viable to use any transport mechanism that you require for you application. The only thing you need to worry about is interoperability with other product implementations of either your client or server end of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the design phase of a File Transfer server (similar to FTP) that will implement its protocol through SOAP.What I mean?That the server will exhange protocol commands with its clients through SOAP-XML envelopes. I have to say I quite familiar with XML parsers and Java too.The whole implementation will be in Java.In tha last 2 weeks I am investigating SOAP through books , web resources , etc. Most of the resources I have found ,are dealing with SOAP as part of the Web Services thing!Thats fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server and clients.Imagine that my envelopes will have some FTP like commands.Thats all.I am in the design phase of the protocol itself , and I am bit stuck in way , on how my messages will be travelling through the wire.The thing that worries me about is tha SOAP is almost bound top HTTP.In my case I dont think that I really need HTTP? What do you think about that?My solution is to send SOAP envelopes, through plain socket /stream connections .The other thing that worries me about is that i still dont know if existing JAVA SOAP libraries like APACHE , JAXM can help me deal easily with SOAP messages that are not bind to HTTP wrapper..has anyone tried something like that?So probably using Apache Xerces I have to provide a mechanism for marshalling and demarshalling my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but in my case I dont think is neccesary.I am really trying to find out , if that use of SOAP can be described as message-style SOAP .For those who might ask why SOAP , you can use any custom XML protocol , I shall answer that is the spec and I cant do anything about that.It is going to be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: SOAP based FTP server , some academic issues, opinions needed!
Posted by Paramdeep Singh <pd...@HotPOP.com>.
MessageHi PAPO,
I am not sure, what you are trying to do!
1) Are you trying to implement functionality of FTP on top of SOAP?
2) Or are you trying to implement "passing of SOAP messages" on top of FTP?
If you are trying to implement (2), then you should look at what Anne is suggesting. But in case you are trying to do (1), then I am not very sure if it is the right thing to do. FTP is a binary protocol, which has many features favouring file transfer. If you try to implement FTP on top of HTTP, then this might not be very efficient.
In case you are targetting any other transport, then I would question, why at all are you not happy with FTP?? FTP is a "standard protocol" and I think is more widely accepted than SOAP! ;)
Warm Regards,
Paramdeep
----- Original Message -----
From: Anne Thomas Manes
To: soap-user@xml.apache.org
Sent: Friday, October 18, 2002 10:59 PM
Subject: RE: SOAP based FTP server , some academic issues, opinions needed!
I suggest that you take a look at Apache Axis (http://xml.apache.org/axis). It provides a really nice transport framework that allows you to send and receive SOAP messages over almost any type of transport. You would also be able to use its serialization services. Apache Axis is very modular, and you should be able to pick and choose which parts of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that made the whole project weird is that I am going to use a very small functionality provided by the SOAP itself.I should describe my try as a messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for my (academic) implementation , might be totally out of the standar and famous way that SOAP is being used now.But that I think is a quite academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions needed!
SOAP was designed to be transport independent. It's only that most of the implementations support http(s) as the default transport. I do know that with Apache you can create your SOAP call and serialize it to a string to use for your own transport. I'm not sure if they support native sockets but I'd be surprised if they don't. I do know that several of the other packages out there in other languages support SMTP/POP, raw sockets, etc as an option. I think it is completely viable to use any transport mechanism that you require for you application. The only thing you need to worry about is interoperability with other product implementations of either your client or server end of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the design phase of a File Transfer server (similar to FTP) that will implement its protocol through SOAP.What I mean?That the server will exhange protocol commands with its clients through SOAP-XML envelopes. I have to say I quite familiar with XML parsers and Java too.The whole implementation will be in Java.In tha last 2 weeks I am investigating SOAP through books , web resources , etc. Most of the resources I have found ,are dealing with SOAP as part of the Web Services thing!Thats fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server and clients.Imagine that my envelopes will have some FTP like commands.Thats all.I am in the design phase of the protocol itself , and I am bit stuck in way , on how my messages will be travelling through the wire.The thing that worries me about is tha SOAP is almost bound top HTTP.In my case I dont think that I really need HTTP? What do you think about that?My solution is to send SOAP envelopes, through plain socket /stream connections .The other thing that worries me about is that i still dont know if existing JAVA SOAP libraries like APACHE , JAXM can help me deal easily with SOAP messages that are not bind to HTTP wrapper..has anyone tried something like that?So probably using Apache Xerces I have to provide a mechanism for marshalling and demarshalling my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but in my case I dont think is neccesary.I am really trying to find out , if that use of SOAP can be described as message-style SOAP .For those who might ask why SOAP , you can use any custom XML protocol , I shall answer that is the spec and I cant do anything about that.It is going to be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by PAPO <pa...@freemail.gr>.
Thanks for your reply!
>From those I have seen till now , i think that Apache SOAP is the most
convenient , because it lets tou deal with the Envelope only in a quite
flexible way , Axis in far more web services oriernted.But anyway when
it comes to dealing only with the plain XML thing , the Axis and Apache
SOAP are offering almost the same flexibility!
Another solution would be a re-inventing the wheel solution , using only
Apache Xerces.Because my protocol is not going to define any huge
envelopes , eg
CD -> ChangeDirectory ( DirName) , I was thinking of creating with
Xerces custom made SOAP envelopes.The thing is I dont know if I am going
to be accused of actually not implementing SOAP in a proper manner!
Thanks again!
A.P
-----Original Message-----
From: Anne Thomas Manes [mailto:anne@manes.net]
Sent: Friday, October 18, 2002 6:30 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
I suggest that you take a look at Apache Axis
(http://xml.apache.org/axis). It provides a really nice transport
framework that allows you to send and receive SOAP messages over almost
any type of transport. You would also be able to use its serialization
services. Apache Axis is very modular, and you should be able to pick
and choose which parts of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that
made the whole project weird is that I am going to use a very small
functionality provided by the SOAP itself.I should describe my try as a
messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite
academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a
string to use for your own transport. I'm not sure if they support
native sockets but I'd be surprised if they don't. I do know that
several of the other packages out there in other languages support
SMTP/POP, raw sockets, etc as an option. I think it is completely
viable to use any transport mechanism that you require for you
application. The only thing you need to worry about is interoperability
with other product implementations of either your client or server end
of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will
implement its protocol through SOAP.What I mean?That the server will
exhange protocol commands with its clients through SOAP-XML envelopes. I
have to say I quite familiar with XML parsers and Java too.The whole
implementation will be in Java.In tha last 2 weeks I am investigating
SOAP through books , web resources , etc. Most of the resources I have
found ,are dealing with SOAP as part of the Web Services thing!Thats
fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like
commands.Thats all.I am in the design phase of the protocol itself , and
I am bit stuck in way , on how my messages will be travelling through
the wire.The thing that worries me about is tha SOAP is almost bound top
HTTP.In my case I dont think that I really need HTTP? What do you think
about that?My solution is to send SOAP envelopes, through plain socket
/stream connections .The other thing that worries me about is that i
still dont know if existing JAVA SOAP libraries like APACHE , JAXM can
help me deal easily with SOAP messages that are not bind to HTTP
wrapper..has anyone tried something like that?So probably using Apache
Xerces I have to provide a mechanism for marshalling and demarshalling
my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who
might ask why SOAP , you can use any custom XML protocol , I shall
answer that is the spec and I cant do anything about that.It is going to
be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by PAPO <pa...@freemail.gr>.
Thanks for your reply!
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by Anne Thomas Manes <an...@manes.net>.
MessageI suggest that you take a look at Apache Axis
(http://xml.apache.org/axis). It provides a really nice transport framework
that allows you to send and receive SOAP messages over almost any type of
transport. You would also be able to use its serialization services. Apache
Axis is very modular, and you should be able to pick and choose which parts
of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that made
the whole project weird is that I am going to use a very small functionality
provided by the SOAP itself.I should describe my try as a messaging
soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite academic
concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a string
to use for your own transport. I'm not sure if they support native sockets
but I'd be surprised if they don't. I do know that several of the other
packages out there in other languages support SMTP/POP, raw sockets, etc as
an option. I think it is completely viable to use any transport mechanism
that you require for you application. The only thing you need to worry
about is interoperability with other product implementations of either your
client or server end of the pipe. If you control both, then the transport
shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will implement
its protocol through SOAP.What I mean?That the server will exhange protocol
commands with its clients through SOAP-XML envelopes. I have to say I quite
familiar with XML parsers and Java too.The whole implementation will be in
Java.In tha last 2 weeks I am investigating SOAP through books , web
resources , etc. Most of the resources I have found ,are dealing with SOAP
as part of the Web Services thing!Thats fine with me.But in my case I have
some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like commands.Thats
all.I am in the design phase of the protocol itself , and I am bit stuck in
way , on how my messages will be travelling through the wire.The thing that
worries me about is tha SOAP is almost bound top HTTP.In my case I dont
think that I really need HTTP? What do you think about that?My solution is
to send SOAP envelopes, through plain socket /stream connections .The other
thing that worries me about is that i still dont know if existing JAVA SOAP
libraries like APACHE , JAXM can help me deal easily with SOAP messages that
are not bind to HTTP wrapper..has anyone tried something like that?So
probably using Apache Xerces I have to provide a mechanism for marshalling
and demarshalling my SOAP over the wire!I know it sounds like reinventing
the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who might
ask why SOAP , you can use any custom XML protocol , I shall answer that is
the spec and I cant do anything about that.It is going to be a weird use of
SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by Anne Thomas Manes <an...@manes.net>.
MessageI suggest that you take a look at Apache Axis
(http://xml.apache.org/axis). It provides a really nice transport framework
that allows you to send and receive SOAP messages over almost any type of
transport. You would also be able to use its serialization services. Apache
Axis is very modular, and you should be able to pick and choose which parts
of the system you'd like to use.
Anne
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 12:46 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that made
the whole project weird is that I am going to use a very small functionality
provided by the SOAP itself.I should describe my try as a messaging
soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite academic
concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a string
to use for your own transport. I'm not sure if they support native sockets
but I'd be surprised if they don't. I do know that several of the other
packages out there in other languages support SMTP/POP, raw sockets, etc as
an option. I think it is completely viable to use any transport mechanism
that you require for you application. The only thing you need to worry
about is interoperability with other product implementations of either your
client or server end of the pipe. If you control both, then the transport
shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will implement
its protocol through SOAP.What I mean?That the server will exhange protocol
commands with its clients through SOAP-XML envelopes. I have to say I quite
familiar with XML parsers and Java too.The whole implementation will be in
Java.In tha last 2 weeks I am investigating SOAP through books , web
resources , etc. Most of the resources I have found ,are dealing with SOAP
as part of the Web Services thing!Thats fine with me.But in my case I have
some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like commands.Thats
all.I am in the design phase of the protocol itself , and I am bit stuck in
way , on how my messages will be travelling through the wire.The thing that
worries me about is tha SOAP is almost bound top HTTP.In my case I dont
think that I really need HTTP? What do you think about that?My solution is
to send SOAP envelopes, through plain socket /stream connections .The other
thing that worries me about is that i still dont know if existing JAVA SOAP
libraries like APACHE , JAXM can help me deal easily with SOAP messages that
are not bind to HTTP wrapper..has anyone tried something like that?So
probably using Apache Xerces I have to provide a mechanism for marshalling
and demarshalling my SOAP over the wire!I know it sounds like reinventing
the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who might
ask why SOAP , you can use any custom XML protocol , I shall answer that is
the spec and I cant do anything about that.It is going to be a weird use of
SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by PAPO <pa...@freemail.gr>.
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that
made the whole project weird is that I am going to use a very small
functionality provided by the SOAP itself.I should describe my try as a
messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite
academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a
string to use for your own transport. I'm not sure if they support
native sockets but I'd be surprised if they don't. I do know that
several of the other packages out there in other languages support
SMTP/POP, raw sockets, etc as an option. I think it is completely
viable to use any transport mechanism that you require for you
application. The only thing you need to worry about is interoperability
with other product implementations of either your client or server end
of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will
implement its protocol through SOAP.What I mean?That the server will
exhange protocol commands with its clients through SOAP-XML envelopes. I
have to say I quite familiar with XML parsers and Java too.The whole
implementation will be in Java.In tha last 2 weeks I am investigating
SOAP through books , web resources , etc. Most of the resources I have
found ,are dealing with SOAP as part of the Web Services thing!Thats
fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like
commands.Thats all.I am in the design phase of the protocol itself , and
I am bit stuck in way , on how my messages will be travelling through
the wire.The thing that worries me about is tha SOAP is almost bound top
HTTP.In my case I dont think that I really need HTTP? What do you think
about that?My solution is to send SOAP envelopes, through plain socket
/stream connections .The other thing that worries me about is that i
still dont know if existing JAVA SOAP libraries like APACHE , JAXM can
help me deal easily with SOAP messages that are not bind to HTTP
wrapper..has anyone tried something like that?So probably using Apache
Xerces I have to provide a mechanism for marshalling and demarshalling
my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who
might ask why SOAP , you can use any custom XML protocol , I shall
answer that is the spec and I cant do anything about that.It is going to
be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: SOAP based FTP server , some academic issues, opinions needed!
Posted by PAPO <pa...@freemail.gr>.
Thanks for your reply.
Yeah actualy I control both sides , client and server .The thing that
made the whole project weird is that I am going to use a very small
functionality provided by the SOAP itself.I should describe my try as a
messaging soap-enabled protocol.
I made my previous post , just to express my fears that , such a try for
my (academic) implementation , might be totally out of the standar and
famous way that SOAP is being used now.But that I think is a quite
academic concern !
Thanks again!
P.A
-----Original Message-----
From: Joe Pruitt [mailto:j.pruitt@f5.com]
Sent: Friday, October 18, 2002 5:28 PM
To: 'soap-user@xml.apache.org'
Subject: RE: SOAP based FTP server , some academic issues, opinions
needed!
SOAP was designed to be transport independent. It's only that most of
the implementations support http(s) as the default transport. I do know
that with Apache you can create your SOAP call and serialize it to a
string to use for your own transport. I'm not sure if they support
native sockets but I'd be surprised if they don't. I do know that
several of the other packages out there in other languages support
SMTP/POP, raw sockets, etc as an option. I think it is completely
viable to use any transport mechanism that you require for you
application. The only thing you need to worry about is interoperability
with other product implementations of either your client or server end
of the pipe. If you control both, then the transport shouldn't matter.
-Joe
-----Original Message-----
From: PAPO [mailto:papo@freemail.gr]
Sent: Friday, October 18, 2002 8:24 AM
To: soap-user@xml.apache.org
Subject: SOAP based FTP server , some academic issues, opinions needed!
Hi!
I would like your opinions or suggestions if available.I am in the
design phase of a File Transfer server (similar to FTP) that will
implement its protocol through SOAP.What I mean?That the server will
exhange protocol commands with its clients through SOAP-XML envelopes. I
have to say I quite familiar with XML parsers and Java too.The whole
implementation will be in Java.In tha last 2 weeks I am investigating
SOAP through books , web resources , etc. Most of the resources I have
found ,are dealing with SOAP as part of the Web Services thing!Thats
fine with me.But in my case I have some concernes!
As you can understand I want only to use SOAP messages , for my server
and clients.Imagine that my envelopes will have some FTP like
commands.Thats all.I am in the design phase of the protocol itself , and
I am bit stuck in way , on how my messages will be travelling through
the wire.The thing that worries me about is tha SOAP is almost bound top
HTTP.In my case I dont think that I really need HTTP? What do you think
about that?My solution is to send SOAP envelopes, through plain socket
/stream connections .The other thing that worries me about is that i
still dont know if existing JAVA SOAP libraries like APACHE , JAXM can
help me deal easily with SOAP messages that are not bind to HTTP
wrapper..has anyone tried something like that?So probably using Apache
Xerces I have to provide a mechanism for marshalling and demarshalling
my SOAP over the wire!I know it sounds like reinventing the wheel.
I really understand the use of HTTP when it comes to Web Services , but
in my case I dont think is neccesary.I am really trying to find out , if
that use of SOAP can be described as message-style SOAP .For those who
might ask why SOAP , you can use any custom XML protocol , I shall
answer that is the spec and I cant do anything about that.It is going to
be a weird use of SOAP anyway!
Thank you in advance
A.P
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>