AmiWest 2013 Lesson 4 - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:31:42Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

← Older revision		Revision as of 19:31, 26 January 2025
Line 34:		Line 34:
	port in question using this format:		port in question using this format:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	TCP:<server URL>/<port number>		TCP:<server URL>/<port number>
	</syntaxhighlight>		</syntaxhighlight>
Line 41:		Line 41:
	use:		use:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	fileh = fopen("TCP:www.wunderground.com/80","r+");		fileh = fopen("TCP:www.wunderground.com/80","r+");
	</syntaxhighlight>		</syntaxhighlight>
Line 85:		Line 85:
	A simple HTTP version 1.1 GET request would include the following lines:		A simple HTTP version 1.1 GET request would include the following lines:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	GET /<path> HTTP/1.1		GET /<path> HTTP/1.1
	host: <domain>		host: <domain>
Line 104:		Line 104:
	Washington's Dulles International Airport with these domain & path values:		Washington's Dulles International Airport with these domain & path values:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	URL = www.wunderground.com		URL = www.wunderground.com
	PATH = cgi-bin/findweather/getForecast?query=IAD		PATH = cgi-bin/findweather/getForecast?query=IAD
Line 113:		Line 113:
	TCP: file handle, as follows:		TCP: file handle, as follows:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	// build web req text		// build web req text
	strcpy(line,"GET /");		strcpy(line,"GET /");
Line 145:		Line 145:
	browser's URL string gadget, like this:		browser's URL string gadget, like this:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	www.wunderground.com/cgi-bin/findweather/getForecast?query=IAD		www.wunderground.com/cgi-bin/findweather/getForecast?query=IAD
	</syntaxhighlight>		</syntaxhighlight>
Line 157:		Line 157:
	lines returned:		lines returned:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	// read in the response		// read in the response
	count = 0;		count = 0;
Line 176:		Line 176:
	simply closing the file handle will close the connection to the server:		simply closing the file handle will close the connection to the server:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	fclose(fileh);		fclose(fileh);
	</syntaxhighlight>		</syntaxhighlight>
Line 194:		Line 194:
	you learned above to upgrade or replace this example.		you learned above to upgrade or replace this example.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/*		/*
	************************************************************		************************************************************
Line 428:		Line 428:
	other file or user input, like this:		other file or user input, like this:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	// read in the response		// read in the response
	while( (fgets(inStr,MAX_STR,(FILE *)stdin) != NULL) && (count<100) )		while( (fgets(inStr,MAX_STR,(FILE *)stdin) != NULL) && (count<100) )
Line 472:		Line 472:
	of a very simple webpage through Roadshow, to our web visitor:		of a very simple webpage through Roadshow, to our web visitor:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	//loop thru text writing to stdout		//loop thru text writing to stdout
	do		do
Line 508:		Line 508:
	the full program here:		the full program here:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/*		/*
	************************************************************		************************************************************
Line 640:		Line 640:
	Configuration of these files is described in the file:		Configuration of these files is described in the file:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	SYS:Documentation/Roadshow/README		SYS:Documentation/Roadshow/README
	</syntaxhighlight>		</syntaxhighlight>
Line 661:		Line 661:
	Such settings could be:		Such settings could be:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	Name = IPserver		Name = IPserver
	Port = 7600		Port = 7600
Line 673:		Line 673:
	(in port number location) into the file "DEVS:Internet/Services":		(in port number location) into the file "DEVS:Internet/Services":

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	IPServer 7600/tcp		IPServer 7600/tcp
	</syntaxhighlight>		</syntaxhighlight>
Line 693:		Line 693:
	our Amiga system. Such settings could be:		our Amiga system. Such settings could be:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	Service = IPserver		Service = IPserver
	Type = Stream		Type = Stream
Line 711:		Line 711:
	following line to the "DEVS:Internet/servers" file:		following line to the "DEVS:Internet/servers" file:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	IPServer stream dos stack=65536 data:Projects/C/OS4ex-IPserver/IPserver.debug		IPServer stream dos stack=65536 data:Projects/C/OS4ex-IPserver/IPserver.debug
	</syntaxhighlight>		</syntaxhighlight>
Line 726:		Line 726:
	enter this in your browser URL line:		enter this in your browser URL line:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	http://localhost:7600/		http://localhost:7600/
	</syntaxhighlight>		</syntaxhighlight>
Line 734:		Line 734:
	look something like this:		look something like this:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	http://192.168.1.07:7600/		http://192.168.1.07:7600/
	</syntaxhighlight>		</syntaxhighlight>
Line 754:		Line 754:
	server, with one of them saying:		server, with one of them saying:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	GET /favicon.ico HTTP/1.1		GET /favicon.ico HTTP/1.1
	</syntaxhighlight>		</syntaxhighlight>

Steven Solie: /* An Internet Client */

2015-10-02T18:52:58Z

An Internet Client

← Older revision		Revision as of 18:52, 2 October 2015
Line 24:		Line 24:

	The Roadshow shortcut we will use is its built-in TCP: handler. This is		The Roadshow shortcut we will use is its built-in TCP: handler. This is
	mechanism that creates a virtual ~~filesystem~~ device ("TCP:") whenever		mechanism that creates a virtual file system device ("TCP:") whenever
	Roadhsow gets online. To interact with a remote server, one3 opens a		Roadhsow gets online. To interact with a remote server, one3 opens a
	file with the name being the URL of the server and port to be accessed.		file with the name being the URL of the server and port to be accessed.

Paul Sadlik: /* General Issues */

2014-05-12T03:24:58Z

General Issues

← Older revision		Revision as of 03:24, 12 May 2014
Line 870:		Line 870:
	be interrupted mid-stream. Received data can be incomplete or corrupted.		be interrupted mid-stream. Received data can be incomplete or corrupted.
	These applications need to have the error trapping to deal with such real		These applications need to have the error trapping to deal with such real
	possibilities.		possibilities - that isn't reflected in the simple examples above.

	====Statelessness====		====Statelessness====

Paul Sadlik: /* Just Webpages? */

2014-05-12T03:22:22Z

Just Webpages?

Paul Sadlik: /* Where to go? Webpages? More? */

2014-05-12T03:11:42Z

Where to go? Webpages? More?

← Older revision		Revision as of 03:11, 12 May 2014
Line 768:		Line 768:
	search the many sources online or in your local bookstore on HTTP communications		search the many sources online or in your local bookstore on HTTP communications
	and the formatting of HTML webpages. Of course, you should make sure your		and the formatting of HTML webpages. Of course, you should make sure your
	server ~~continues~~ ~~outputting~~ ~~the~~ ~~request~~ ~~contents~~ so you know what ~~your~~ ~~server~~		server can optionally send diagnostics output so you know what requests are
	is ~~getting~~ and ~~should~~ ~~respond~~ to.		being received and how they are responded to.

	===Just Webpages?===		===Just Webpages?===

Paul Sadlik: /* Where to go? More Webpages? */

2014-05-12T03:09:33Z

Where to go? More Webpages?

Paul Sadlik: /* Let's See Our Server! */

2014-05-12T03:06:53Z

Let's See Our Server!

← Older revision		Revision as of 03:06, 12 May 2014
Line 738:		Line 738:
	</syntaxhighlight>		</syntaxhighlight>

	In any case, the browser will connect to your Amiga at the port number		In any case, the browser will connect to your Amiga (at the port number
	following the colon (":") and Roadshow will call up your server program		following the colon - ":") and Roadshow will call up your server program
	and let it talk to your browser and send it the preset webpage.		and let it talk to your browser and send it the preset webpage.

Paul Sadlik: /* Roadshow Configuration */

2014-05-12T02:58:38Z

Roadshow Configuration

← Older revision		Revision as of 02:58, 12 May 2014
Line 635:		Line 635:

	There are two areas where Roadshow needs to be told about your server		There are two areas where Roadshow needs to be told about your server
	and the service it is going to provide. Both of these can ~~be configured~~		and the service it is going to provide, as described below. Both of these can
	using Internet Prefs. You can also make this configuration by ~~editing~~		be configured using Internet Prefs. You can also make this configuration by
	the "servers" and "services" files in the "DEVS:internet/" directory.		manually editing the "servers" and "services" files in the "DEVS:internet/" directory.
	Configuration of these files is described in the file:		Configuration of these files is described in the file:

	<syntaxhighlight>		<syntaxhighlight>
	SYS:Documentation?Roadshow/README		SYS:Documentation/Roadshow/README
	</syntaxhighlight>		</syntaxhighlight>

Line 670:		Line 670:
	"Save" in Internet Prefs, this service will be recognized by Roadshow.		"Save" in Internet Prefs, this service will be recognized by Roadshow.

	The same configuration could be added to Roadshow by adding this line		The same configuration could manually be added to Roadshow by adding this line
	(in port number location) into the file "DEVS:Internet/Services":		(in port number location) into the file "DEVS:Internet/Services":

Line 708:		Line 708:
	Prefs will adjust Roadshow.		Prefs will adjust Roadshow.

	We can ~~also~~ make this adjustment to Roadshow's server list by adding the		We can otherwise make this adjustment to Roadshow's server list by manually adding the
	following line to the "DEVS:Internet/servers" file:		following line to the "DEVS:Internet/servers" file:

Paul Sadlik: /* EXAMPLE TWO: IPserver.c */

2014-05-12T02:47:37Z

EXAMPLE TWO: IPserver.c

← Older revision		Revision as of 02:47, 12 May 2014
Line 629:		Line 629:
	serving your Amiga's internet visitors.		serving your Amiga's internet visitors.

	But how do we test this ~~all~~ out? First we have to let Roadshow know that		But how do we test this server out? First we have to let Roadshow know that
	we've created this server and where visitors will find it.		we've created this server and where visitors will find it.
	''Italic text''

	===Roadshow Configuration===		===Roadshow Configuration===

Paul Sadlik: /* Respond to the Visitor */

2014-05-12T02:30:54Z

Respond to the Visitor

← Older revision		Revision as of 02:30, 12 May 2014
Line 469:		Line 469:
	our web visitor.		our web visitor.

	In this example, we create a basic loop that feeds a predefined series of lines		In this example, we create a basic loop that feeds a predefined series of strings (in the '''lines''' array)
	of a very simple webpage to Roadshow ~~and~~ our web visitor:		of a very simple webpage through Roadshow, to our web visitor:

	<syntaxhighlight>		<syntaxhighlight>
Line 499:		Line 499:
	stream and quit our program.		stream and quit our program.

			While our two samples of code simply receive and respond to an incoming web request,
	The request was received, our little webpage sent, we quit and Roadshow takes
			one can imagine where this code can be expanded provide useful service and more
	care of all the housekeeping.
			complex interactions.

	===EXAMPLE TWO: IPserver.c===		===EXAMPLE TWO: IPserver.c===

← Older revision		Revision as of 03:22, 12 May 2014
Line 773:		Line 773:
	===Just Webpages?===		===Just Webpages?===

	There's also ne reason why your server needs to be limited to dealing		There's also no reason why your server needs to be limited to dealing
	with browsers and sending webpages. The internet is full of other		with browsers and sending webpages. The internet is full of other
	protocols and services that ~~your~~ could write a server for. Or you could		protocols and services that you could write a server for. Or you could
	create your own online client and server pair of applications that ~~just~~		create your own online client and server pair of applications that
	talked with each other.		talked with each other.

Line 793:		Line 793:
	Don't blindly serve sensitive information to visitors. How can you be		Don't blindly serve sensitive information to visitors. How can you be
	sure who's at the other end of the connection and who might be watching		sure who's at the other end of the connection and who might be watching
	along the way? Even if randomized path names and ~~request~~ are used by		along the way? Even if randomized path names and requests are used by
	your server, there's no guarantee the connection is 100% secure.		your server, there's no guarantee the connection is 100% secure.

Line 806:		Line 806:

	One has to keep in mind the "SuperServer" method where Roadshow runs		One has to keep in mind the "SuperServer" method where Roadshow runs
	your server also means your server will be executed with each and every		your server also means your server program will be executed with each and every
	request Roadshow receives for that port. In each case, your server		request Roadshow receives for that port. In each case, your server
	will do its duty and then be expected to quit. That should be fine for		will do its duty and then be expected to quit. That should be fine for
Line 819:		Line 819:
	communications (such as ARexx messages) to interact with a separate		communications (such as ARexx messages) to interact with a separate
	master program that handles all the housekeeping and remains continuously running		master program that handles all the housekeeping and remains continuously running
	while each of internet server ~~instance~~ handles an incoming request, ~~gets the information it~~		while each instance of the internet server handles each incoming request, quickly
	~~needs~~ from the master program and quits.		relays the necessary information from the master program and quits.

	Naturally, at some point usage requirements may require one bypasses the		Naturally, at some point usage requirements may require one bypasses the
	Roadshow SuperServer method of running servers and goes to using		Roadshow SuperServer method of running servers and goes to using
	longhand socket programming that is better suited to heavy duty use		longhand socket programming that is better suited to heavy duty use
	- like running a serious public server. That's beyond the scope of this ~~article~~.		- like running a serious public server. That's beyond the scope of this tutorial.

	Furthermore, there are whole areas of study and technology involved with the		Furthermore, there are whole areas of study and technology involved with the
Line 839:		Line 839:
	protocol are likely to be.		protocol are likely to be.

	As mentioned in elsewhere in this text, there RFC's that describe the		As mentioned in elsewhere in this text, there are RFC's that describe the
	formal protocols and there are likely countless webpages that address		formal protocols and there are likely countless webpages that address
	idiosyncrasies of implementing the protocols.		idiosyncrasies of implementing the protocols.

← Older revision		Revision as of 03:09, 12 May 2014
Line 742:		Line 742:
	and let it talk to your browser and send it the preset webpage.		and let it talk to your browser and send it the preset webpage.

	===Where to go? ~~More~~ Webpages?===		===Where to go? Webpages? More?===

	Clearly the above example does little more than say "Hello World" to a		Clearly the above example does little more than say "Hello World" to a
Line 758:		Line 758:
	</syntaxhighlight>		</syntaxhighlight>

	In that case, the browser is requesting your server send an ~~icon~~		In that case, the browser is requesting your server send an image file
	that it can display on the browser tab. Just like that, anything in the URL		that it can display on the browser tab. Just like that, anything in the URL
	after the machine's network name (or IP address) and the port number		after the machine's network name (or IP address) and the port number
Line 765:		Line 765:

	This just scratches the surface of requests your server may receive and		This just scratches the surface of requests your server may receive and
	how it can respond to web visitors. To dig deeper you can ~~search the~~		how it can process them and respond to web visitors. To dig deeper you can
	many sources online or in your local bookstore on HTTP communications ~~and~~		search the many sources online or in your local bookstore on HTTP communications
	the formatting of HTML webpages. Of course, you should make sure your		and the formatting of HTML webpages. Of course, you should make sure your
	server continues outputting the request contents so you know what your server		server continues outputting the request contents so you know what your server
	is getting and should respond to.		is getting and should respond to.