From 6e08f398200de8a1560e14cdb4fb6c278a8e2b94 Mon Sep 17 00:00:00 2001 From: friendica Date: Sat, 21 Jul 2012 03:48:59 -0700 Subject: simplify --- library/phpsec/intro.html | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 library/phpsec/intro.html (limited to 'library/phpsec/intro.html') diff --git a/library/phpsec/intro.html b/library/phpsec/intro.html deleted file mode 100644 index 406b22fc5..000000000 --- a/library/phpsec/intro.html +++ /dev/null @@ -1,20 +0,0 @@ - - -Chapter 1. Introduction

Chapter 1. Introduction

1.1. Who should use phpseclib

- Although many of the features this library implements are implemented in PHP via optional extensions, what are - you, as a developer, going to do when a user tries to run your software on a host which, coincidentally, doesn't - happen to have that optional extension installed? You could, flat-out, tell that user to look for another - software package that does work on their server (or to get another host, or whatever), which is liable to leave - a bad impression on the user, or you could use a library like this - a library that uses those optional - extensions if they're available and falls back on an internal PHP implementation if they're not. -

- Another advantage of using this library over optional PHP extensions is that you, as a developer, may find this - libraries API easier to use then extensions API. -

1.2. Using phpseclib

- This library is written using the same conventions that libraries in the PHP Extension and Application Repository (PEAR) - have been written in. In particular, this library expects to be in your include_path: -

<?php
-set_include_path(get_include_path() . PATH_SEPARATOR . 'phpseclib');
-
-include('Net/SSH2.php');
-?>
-- cgit v1.2.3