IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Why not HTTP?
I'm looking more for reasons not to do HTTP as well, I guess.

What is wrong with HTTP? Anything else and you risk fire-wall problems. Server admins don't like special requests for "odd ports" at many companies. Simply use POST to send XML or comma-delimited text.
________________
oop.ismad.com
New Read the problem description.
No firewalls are involved. While you are correct that firewalls preclude anything other than HTTP for the most part, this is entirely internal on our LAN.

If you want to have real fun, try building a bi-directional persistent comm link between a client browser and an internal server through a firewall, when the internal server is actually a load-balanced non-clustered web farm. ;-)
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New You didn't qualify "too much overhead"
Nothing is going to be an exact match to your desired performance or interface requirements.

If you are sending streams of a gazillion little transactions, can some of them be grouped together so that packet overhead is less? Or, does each one need a reply before the next one is sent?

These details are left out.
________________
oop.ismad.com
New Packet overhead doesn't matter.
Computational overhead does matter.

The transactions are uncoupled.
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
     Communication between two servers. - (admin) - (39)
         SOAP - (ChrisR) - (8)
             Right, that's what I'm trying to avoid. - (admin) - (1)
                 Welcome to my life -NT - (drewk)
             Stupid Object Asskiss Protocol -NT - (tuberculosis) - (5)
                 SOAP is one those decent ideas... - (ChrisR) - (4)
                     A decent idea? - (ben_tilly) - (2)
                         Valid complaint - (ChrisR)
                         In fairness, - (Arkadiy)
                     No, she's a dog - (tuberculosis)
         Quick alphabet soup translation: - (jb4) - (2)
             Java Messaging Service - (admin) - (1)
                 Danke -NT - (jb4)
         roll own xinted service? - (deSitter)
         Just remember--anything manual can be automated - (FuManChu) - (5)
             Well, that's what I meant. - (admin)
             I lean towards sockets as well - (tjsinclair) - (3)
                 Remember there's C++ on the other end. - (admin) - (2)
                     Name one: - (folkert) - (1)
                         I'm guessing the answer will be: - (admin)
         4. CORBA connection but same objection as JMS Go with socket -NT - (boxley)
         My Gut reaction tells me: - (folkert) - (9)
             We have plenty of socket servers here already. - (admin) - (8)
                 Sockets can stream, http does not, its connectionless - (boxley) - (1)
                     HTTP 1.1 supports pipelining, FYI. -NT - (admin)
                 YALOP - (folkert) - (1)
                     Agreed - (deSitter)
                 Why not HTTP? - (tablizer) - (3)
                     Read the problem description. - (admin) - (2)
                         You didn't qualify "too much overhead" - (tablizer) - (1)
                             Packet overhead doesn't matter. - (admin)
         DECNet Mailboxes. - (pwhysall) - (2)
             AHHH! NO!!! - (deSitter) - (1)
                 Silence, heretic. - (pwhysall)
         Socket to me - (tuberculosis) - (4)
             Why the daemon: - (admin) - (3)
                 Not an answer then, but a plan of attack :) - (FuManChu) - (2)
                     Complicated political situation. - (admin) - (1)
                         You mean you're not king? - (tuberculosis)
         Tuxedo/Java Jolt? - (gdaustin)

You signed the Memo of Understanding...!
62 ms