<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://solarstrike.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Network_Module</id>
		<title>Network Module - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://solarstrike.net/wiki/index.php?action=history&amp;feed=atom&amp;title=Network_Module"/>
		<link rel="alternate" type="text/html" href="https://solarstrike.net/wiki/index.php?title=Network_Module&amp;action=history"/>
		<updated>2026-05-01T09:44:54Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://solarstrike.net/wiki/index.php?title=Network_Module&amp;diff=1180&amp;oldid=prev</id>
		<title>Elverion: Created page with &quot;See also: Socket Class  == Network Events == Due to the asynchronous nature of networking, a lot of networking information will only be available through the event system....&quot;</title>
		<link rel="alternate" type="text/html" href="https://solarstrike.net/wiki/index.php?title=Network_Module&amp;diff=1180&amp;oldid=prev"/>
				<updated>2014-12-12T18:16:18Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;See also: &lt;a href=&quot;/wiki/index.php/Socket_Class&quot; title=&quot;Socket Class&quot;&gt;Socket Class&lt;/a&gt;  == Network Events == Due to the asynchronous nature of networking, a lot of networking information will only be available through the event system....&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;See also: [[Socket Class]]&lt;br /&gt;
&lt;br /&gt;
== Network Events ==&lt;br /&gt;
Due to the asynchronous nature of networking, a lot of networking information will only be available through the event system. For example, when a socket receives data, a new event will be pushed that contains the socket ID and the contents of the message.&lt;br /&gt;
&lt;br /&gt;
Relevant events are: socketconnected, socketdisconnected, socketreceived, and socketerror. For a full description of of these events, see the [[Events]] page. The important thing to remember is that the socketconnected event will push a new '''socket object''' while other socket events will only push a '''socket ID'''. As such, you should be sure to save the new socket object (preferably into a table) if your script will be accepting new connections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== socket ==&lt;br /&gt;
'''socket network.socket([string &amp;quot;tcp&amp;quot;|&amp;quot;udp&amp;quot;])'''&lt;br /&gt;
&lt;br /&gt;
Create a new socket object. This object will be used to actually open a connection and transmit data. Accepts only one string which determines the protocol type: &amp;quot;tcp&amp;quot; or &amp;quot;udp&amp;quot;; defaults to TCP if not given.&lt;/div&gt;</summary>
		<author><name>Elverion</name></author>	</entry>

	</feed>