Discussion Locked

MSMQ over Internet Example

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am looking for a simple real-life message queing example that can exchange small messages of 1K or less to ASCII files of 50MB or more, asynchronously, that will run over the internet (computers not in domain or even workgroup).

All computersare Windows 2000. VB is the preferred language.

Purpose is educational, so example should be easy, documented and tryable.

Pointers to someone else's answer would also help.

Points will be increased (a lot) for viable answer.

5 replies

by jay eckles

Hmmm...exchanging small messages of 1k or less to 50 MB or more asynchronously over the internet...

Sounds like Email to me.

Here's a link to the SMTP RFC 821:
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc0821.html
Here's a link to a simple VB implementation of an SMTP client:
http://www.vbip.com/winsock/winsock_simple_sender.asp
Here's a link to an ActiveX (maybe VB, maybe another COM language) implementation of an SMTP server:
http://homepages.com.pk/kashman/SMTP.htm
A search on Google will reveal many more links I'm sure.

I don't know if you can find a better example. For educational purposes, it's perfect because most people are familiar with email already, so you don't have to waste your time explaining the functionality. Implementations go from very simple to extremely complex. There are tutorials everywhere on how to write SMTP servers and clients. Even better, your simple clients and servers will work just fine with existing commercial clients and servers, so students can actually use a project they create.

Good luck.

Jay
www.jayeckles.com

by bg22

I actually have two applications that need to exchange data. The data may be anywhere from a few transactions to several hundred thousand transactions in CSV, EDI or XML files. Many factors contribute to the wide variance of volume. No humans areinvolved. The files come into the one side at random intervals at the rate of one every few seconds to one evey few hours. We can't aford to lose any so we want to gueue them on the originating side until we are sure the receiving side has received them and we want to queue them on the receiving side until we are sure they are properly processed in the right sequence.

by jay eckles

Hmmm...exchanging small messages of 1k or less to 50 MB or more asynchronously over the internet...

Sounds like Email to me.

Here's a link to the SMTP RFC 821:
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc0821.html
Here's a link to a simple VB implementation of an SMTP client:
http://www.vbip.com/winsock/winsock_simple_sender.asp
Here's a link to an ActiveX (maybe VB, maybe another COM language) implementation of an SMTP server:
http://homepages.com.pk/kashman/SMTP.htm
A search on Google will reveal many more links I'm sure.

I don't know if you can find a better example. For educational purposes, it's perfect because most people are familiar with email already, so you don't have to waste your time explaining the functionality. Implementations go from very simple to extremely complex. There are tutorials everywhere on how to write SMTP servers and clients. Even better, your simple clients and servers will work just fine with existing commercial clients and servers, so students can actually use a project they create.

Good luck.

Jay
www.jayeckles.com

by jay eckles

In response to your comment - read the SMTP RFC. Email messages are queued at the sending side until they have been received - the SMTP server will attempt multiple times to try to deliver a message. Likewise, the messages are queued at the receiving SMPT server until the client fetches them.

If you want to do some processing at either end, just add that code to your SMTP client(s).

As you can tell, I still don't see why SMTP doesn't meet your requirements.

Good luck.

Jay

This discussion is closed to new replies.