Teaching Indigo to do REST/POX: Part 7
<A title=http://staff.newtelligence.net/clemensv/PermaLink,guid,2d61b97b-3a6e-46bd-89db-b1b20499ba18.aspx href="http://staff.newtelligence.net/clemensv/PermaLink,guid,2d61b97b-3a6e-46bd-89db-b1b20499ba18.aspx"><SPAN lang=EN-US><SPAN title=http://staff.newtelligence.net/clemensv/PermaLink,guid,2d61b97b-3a6e-46bd-89db-b1b20499ba18.aspx>Part 1</SPAN></A></SPAN>, <A title=http://staff.newtelligence.net/clemensv/PermaLink,guid,4e2a7d26-342c-4402-8000-a0d15860c5fc.aspx href="http://staff.newtelligence.net/clemensv/PermaLink,guid,4e2a7d26-342c-4402-8000-a0d15860c5fc.aspx"><SPAN lang=EN-US><SPAN title=http://staff.newtelligence.net/clemensv/PermaLink,guid,4e2a7d26-342c-4402-8000-a0d15860c5fc.aspx>Part 2</SPAN></A></SPAN>, <A title=http://staff.newtelligence.net/clemensv/PermaLink,guid,3f40268c-dee2-44eb-829a-f621a4d40fbc.aspx href="http://staff.newtelligence.net/clemensv/PermaLink,guid,3f40268c-dee2-44eb-829a-f621a4d40fbc.aspx"><SPAN lang=EN-US><SPAN title=http://staff.newtelligence.net/clemensv/PermaLink,guid,3f40268c-dee2-44eb-829a-f621a4d40fbc.aspx>Part 3</SPAN></A></SPAN>, <A title=http://staff.newtelligence.net/clemensv/PermaLink,guid,c45eb508-2269-4d0e-a730-dbd9c7d5f882.aspx href="http://staff.newtelligence.net/clemensv/PermaLink,guid,c45eb508-2269-4d0e-a730-dbd9c7d5f882.aspx"><SPAN lang=EN-US><SPAN title=http://staff.newtelligence.net/clemensv/PermaLink,guid,c45eb508-2269-4d0e-a730-dbd9c7d5f882.aspx>Part 4</SPAN></A></SPAN>, <A title=http://staff.newtelligence.net/clemensv/PermaLink,guid,3712ee6b-cd80-4db3-a96c-c740491f588e.aspx href="http://staff.newtelligence.net/clemensv/PermaLink,guid,3712ee6b-cd80-4db3-a96c-c740491f588e.aspx">Part 5</A>, Part 6, Part 7, Part 8, Part 9
Where are we?
· In Parts 1 and 2, I explained contracts in the REST/POX context and the...
Maximum message size: Unlimited.
In case you are not following my Indigo REST/POX series, I quote one paragraph from today's Part 7 that is well worth to be quoted out of context. It talks about (SOAP-) messages and the misconception that a message is a small thing:
There’s no specification that says that you cannot stick 500 Terabyte or 500 Exabyte worth of data (think 365x24 live 1080i video streams) into a single message. As...
Ah, yes, that’s like Hospital TV
Sabine and I were just browsing Channel 9 using TVTonic on our Media Center PC that's been recently connected to this christmas gift. We watched a few snippets of Microsoft PMs and other folks presenting their latest stuff and then that. Sabine (she's a nurse) said "...oh, that's like Hospital TV".
I can't help but admit that she does indeed have more than just one point in saying that.
Teaching Indigo to do REST/POX: Part 6
<SPAN lang=EN-US>Part 1</SPAN>, <SPAN lang=EN-US>Part 2</SPAN>, <SPAN lang=EN-US>Part 3</SPAN>, <SPAN lang=EN-US>Part 4</SPAN>, Part 5
I threw a lot of unexplained code at you in Part 5 and that wasn’t really fair.
The PoxEncoder class is a replacement for Indigo’s default TextMessageEncoder class that’s used by the HTTP transport unless you explicitly configure something different. Indigo comes with three built-in encoders, namely:
[Read more]
Managed TCP port-forwarder
I recently needed a TCP port-forwarder that sits on a socket connection and monitors it. My concrete use-case is that I need to front the backend-server of my TV application with such a port forwarder in order to create live-TV streaming sessions as soon as a client requests them and also tears them down shortly after the client disconnects so that the session doesn’t need to time out and blocks the tuner until...