Internal things

Many routines in POT are done to hide some inconviences from user. However they could be very interesting for advanced coders which might want to optimise their codes to use more internal POT mechanisms in order to speed up their extensions and reduce their resources usage. If you are not interested in such things - you don't have to know anything from this tutorial, don't worry.

OTS_Base_DAO

This class contains basic object initialisatin for classes that work with database. If you create such class you won't have to worry about database handle fetching (it's constructor will load it into $this->db as well as object storing in session with __sleep() and __wakeup().

OTS_Row_DAO

A bit more automation and interface logic is implemented in OTS_Row_DAO class. It declares loading load() (for ID-based loading) and find() (for name-based loading). It also defines constructor to handle object initialisation with integer and string values.

OTS_Base_List

Base list class defines complete records set handling interface and mechanisms. If you want to create class to handle your table as list of records all you have to do is to define init() method (this method will be automaticly called on object creation) which will set two fields of list object: $this->table which shows table name and $this->class which defines class name for single record class (usualy OTS_Row_DAO child class). However class name must start with OTS_ prefix and $this->class field must only contain it's next part.

OTS_Buffer

PHP contains many string functions but unfortunately strings are not treated as character arrays (not completly) like in C++ for instance. OTS_Buffer class provides method to wrap string within read/write stream. It can be used also as stack since it's read and write pointers are separated.

OTS_FileLoader

Currently there are only two formats that bases on OTServ binary tree - OTBM for maps and OTB for items.otb file. Both of them are supported by currently available POT classes. However POT has generic class for binary formats so in case of any further formats or just a need to support custom format you can create child class that will handle loaded nodes tree - root node is available in $this->root.

OTS_FileNode

Binary files are based on nodes - under root node there is child node which has siblings and possible other child nodes. Each node is represented by single object in POT - object of OTS_FileNode class. It is child class of OTS_Buffer - it's properties can be read directly from it using OTS_Buffer methods. It additionaly contains tree-relations methods - getNext() for next sibling (node of same level) and getChild() for first child node (to get next child nodes you just get first child's siblings).

Database drivers

POT supports all database engines supported by OTServ. However you might want to run OTServ on different database, or simply create some kind of extended driver that will handle some of operations different way. Base class for database driver is OTS_Base_DB which defines default methods for SQL-standard way of methods which POT requires in addition to PDO layer (handling identifier names and LIMIT/OFFSET clauses).

IOTS_Cipher

There are also cipher (encryption/decryption) classes. They handles mainly OTAdmin connection but basicly they are independent and can simply encrypt/decrypt any message. They implements common cipher interface which defines simple interface for cipher classes. In case of any other encryption you would want to use just implement that interface and it will be very simple to bind it with POT tools like OTAdmin client.

Note: RSA cipher class can only encrypt messages as POT is used only on client part. There is no need to provide RSA decryption, but in case you would need that, just rewrite it's decrypt() method.