[
Lists Home |
Date Index |
Thread Index
]
- From: Martin West <martin@thecla.freeserve.co.uk>
- To: Anthony Marino <anthony@nlink.com>,'Joshua Allen ' <joshuaa@microsoft.com>,"''Narayanan, Ramesh' '" <RNarayanan@panasonicfa.com>, xml-dev@xml.org
- Date: Thu, 13 Jul 2000 20:07:20 +0100
Or you could use a JMS http://java.sun.com/products/jms/index.html
implementation like the one provided by SpiritSoft
http://www.spirit-soft.com
and use the push technologies.
Martin West
VP of Engineering
SpiritSoft
replyto: Martin.West@spirit-soft.com
----- Original Message -----
From: Anthony Marino <anthony@nlink.com>
To: 'Joshua Allen ' <joshuaa@microsoft.com>; ''Narayanan, Ramesh' '
<RNarayanan@panasonicfa.com>; <xml-dev@xml.org>
Sent: Friday, July 07, 2000 5:21 AM
Subject: RE: XML across varied Servers
> Check sonicMQ out.
>
> -----Original Message-----
> From: Joshua Allen
> To: 'Narayanan, Ramesh'; 'xml-dev@xml.org'
> Sent: 7/6/00 9:03 PM
> Subject: RE: XML across varied Servers
>
> MQSeries and MSMQ are the best way to move XML documents
> asynchronously. However, there are many other ways you
> can accomplish asynchronous transfer of XML documents.
>
> Some possibilities:
> * Set up a file share on NT, use samba on UNIX to
> place the file on the share. Use NT "at" scheduler
> to periodically check for and process new files.
> If going from NT to UNIX, use cron.
>
> * Drop xml files on an NFS-shared volume and use
> NT SFU to grab from UNIX periodically.
>
> * Use FTP to push or pull the files periodically.
>
> * Use SMTP (some sort of command-line sendmail utility
> on UNIX) to send the file, use CDO on NT to read the
> messages from e-mail periodically.
>
> * Use a database-access library on UNIX to stuff
> the XML documents in rows in a relational database
> (SQL Server, DB2, etc. -- whatever you have).
> Use ADO on the NT side to pull out records as they
> arrive.
>
> There are many, many ways that you can accomplish
> asynchronous transfer of XML documents -- those are just
> a few. When you write your own, though, think hard
> about how your system will behave in failure situations,
> concurrency, etc. With the last option I mentioned
> (database), at least you get serialization, transactional
> control on reads and writes, and so on. If you are doing
> your own scheme with FTP, what happens for example if
> the connection gets dropped partway through transfer?
> You have to write quite a bit of plumbing yourself; that
> is why message queuing software is so popular; you get
> all that stuff for free.
>
> Joshua Allen
> Microsoft eBusiness West Region
> "No challenge can withstand the assault of sustained thinking" -
> Voltaire
>
>
> > -----Original Message-----
> > From: Narayanan, Ramesh [mailto:RNarayanan@panasonicfa.com]
> > Sent: Thursday, July 06, 2000 2:39 PM
> > To: 'xml-dev@xml.org'
> > Subject: XML across varied Servers
> >
> >
> >
> > Hello everybody,
> >
> > I understand that XML is great for moving data across
> > applications
> > running under different OS. Every book and article says this
> > is the primary
> > goal of XML. But i dont understand how this is implemented. More
> > specifically , i need to send an XML document asynchronously
> > from an Unix
> > Server to a Windows NT Server, neither of them running a web
> > server. How can
> > this be done, without using MSMQ or MQSeries ? Could
> > somebody throw some
> > light on this ?
> >
> > Thanks in advance,
> > Ramesh
> >
> > **************************************************************
> > *************
> > This is xml-dev, the mailing list for XML developers.
> > To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
> > List archives are available at http://xml.org/archives/xml-dev/
> > **************************************************************
> > *************
> >
>
> ************************************************************************
> ***
> This is xml-dev, the mailing list for XML developers.
> To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
> List archives are available at http://xml.org/archives/xml-dev/
> ************************************************************************
> ***
>
>
***************************************************************************
> This is xml-dev, the mailing list for XML developers.
> To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
> List archives are available at http://xml.org/archives/xml-dev/
>
***************************************************************************
>
|