Hi,

I am trying to write a client handler for communication between a
client and a server based on a predifined XML protocol. The protocol
is already defined , all I am looking for is a way for me to send and
recieve messages which would be XML based. I am looking to use Java
.Can someone help me with this .

Thanks

[ Post a follow-up to this message ]

raj20013@yahoo.co.in (Raj) writes:

> Hi,
>
> I am trying to write a client handler for communication between a
> client and a server based on a predifined XML protocol. The protocol
> is already defined , all I am looking for is a way for me to send and
> recieve messages which would be XML based. I am looking to use Java
> .Can someone help me with this .

XML is a markup language, not a protocol.  Search google groups for
xml and my name for reasons not to use it.

--
Måns Rullgård
mru@mru.ath.cx

[ Post a follow-up to this message ]

raj20013@yahoo.co.in (Raj) writes:

> I am trying to write a client handler for communication between a
> client and a server based on a predifined XML protocol. The protocol
> is already defined , all I am looking for is a way for me to send
> and recieve messages which would be XML based. I am looking to use
> Java .Can someone help me with this .

There are classes for this available at java.sun.com.

However, as Mans suggested, if you can get out of using XML you'll
probably be better off with another protocol, unless you're selling
bandwidth or cpu :-)

Joe
--
Nothing cures like time and love
- Laura Nyro

[ Post a follow-up to this message ]

In article <yw1xis96ebew.fsf@ford.guide>,
Måns Rullgård <mru@mru.ath.cx> wrote:

> raj20013@yahoo.co.in (Raj) writes:
> 
>
> XML is a markup language, not a protocol.  Search google groups for
> xml and my name for reasons not to use it.

If the specification of the application protocol says that the data is
encoded as XML markup, then it's effectively part of the protocol.  And
it doesn't sound like the OP is designing the protocol, he's just
writing a client for an existing protocol, so the reasons for not using
it are irrelevant to him -- if he wants to access the server, he has to
talk its language.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[ Post a follow-up to this message ]

Barry Margolin <barmar@alum.mit.edu> writes:

> In article <yw1xis96ebew.fsf@ford.guide>,
>  Måns Rullgård <mru@mru.ath.cx> wrote:
> 
>
> If the specification of the application protocol says that the data is
> encoded as XML markup, then it's effectively part of the protocol.  And
> it doesn't sound like the OP is designing the protocol, he's just
> writing a client for an existing protocol, so the reasons for not using
> it are irrelevant to him -- if he wants to access the server, he has to
> talk its language.

Well, in that case I can't but feel sorry for him.  He'll have many
hours of nightmarish fights to look forward to.

--
Måns Rullgård
mru@mru.ath.cx

[ Post a follow-up to this message ]

Måns Rullgård wrote:

> raj20013@yahoo.co.in (Raj) writes:
>
> 
>
>
> XML is a markup language, not a protocol.  Search google groups for
> xml and my name for reasons not to use it.
>

Could you please summarize.  I found a long thread discussing a
proposal to use XML for config files that digressed into a discussion
of protocol but frankly haven't got the time nor inclination to
deconvolve it and try to discover your points.

If your point is that the M in XML doesn't stand for Magic I agree 100%.

If he had said XDR rather than XML would you have reacted differently?

-- ced

--
Chuck Dillon
Senior Software Engineer
NimbleGen Systems Inc.

[ Post a follow-up to this message ]

Chuck Dillon <spam@nimblegen.com> writes:

> Måns Rullgård wrote:
> 
>
> Could you please summarize.  I found a long thread discussing a
> proposal to use XML for config files that digressed into a discussion
> of protocol but frankly haven't got the time nor inclination to
> deconvolve it and try to discover your points.
>
> If your point is that the M in XML doesn't stand for Magic I agree 100%.

Something like that.

> If he had said XDR rather than XML would you have reacted differently?

Possibly.

--
Måns Rullgård
mru@mru.ath.cx

[ Post a follow-up to this message ]

>> raj20013@yahoo.co.in (Raj) writes: 
[vbcol=seagreen]
> Måns Rullgård <mru@mru.ath.cx> wrote: 

Barry Margolin  <barmar@alum.mit.edu> wrote:[vbcol=seagreen]
>If the specification of the application protocol says that the data is
>encoded as XML markup, then it's effectively part of the protocol.

You're both right.  XML is not a protocol.  A number of protocols use XML fo
r
encoding of both payload and protocol info.  The original poster didn't ask 
a
very answerable question, which leads to a wider variety of responses
(including "I hate XML") than is perhaps desired.

Raj, knowing that a protocol uses xml for its data is not really enough to
help with implementing a client.  What specifically are you stuck on, and wh
at
level and type of answer are you looking for?

For instance, are you looking for help in reading or creating payloads based
on a well-known public schema?  Are you looking for networking help in
actually sending/recieving messages (so XML is just a side-issue)?  Are you
hoping to find a library that implements the complete protocol?

Providing a lot more detail (especially the actual protocol description and
name, and how far you've gotten in using it) in your question is likely to
provide far better answers.
--
Mark Rafn    dagon@dagon.net    <http://www.dagon.net/>

[ Post a follow-up to this message ]

In article <d0ii42-8qv.ln1@hydra.dagon.net>,
dagon@dagon.net (Mark Rafn) wrote:
 
> 
>
> Barry Margolin  <barmar@alum.mit.edu> wrote: 
>
> You're both right.  XML is not a protocol.  A number of protocols use XML 
for
> encoding of both payload and protocol info.  The original poster didn't as
k a
> very answerable question, which leads to a wider variety of responses
> (including "I hate XML") than is perhaps desired.

I thought his question was very "answerable".  I think he's basically
just looking for a library to assist in creating and parsing XML data,
much like the libraries that are used for XDR or ASN.1.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[ Post a follow-up to this message ]

Barry Margolin wrote:
> In article <d0ii42-8qv.ln1@hydra.dagon.net>,
>  dagon@dagon.net (Mark Rafn) wrote:
>=20
>=20 
[vbcol=seagreen] 
d[vbcol=seagreen] 
=20[vbcol=seagreen] 
ML for[vbcol=seagreen] 
ask a[vbcol=seagreen] 
>=20
>=20
> I thought his question was very "answerable".  I think he's basically=20
> just looking for a library to assist in creating and parsing XML data, =

> much like the libraries that are used for XDR or ASN.1.

Modern ASN.1 compilers allow a programmer to encode and decode the data
using XML.

--=20
Lev Walkin
vlm@lionet.info

[ Post a follow-up to this message ]