note 85429 added to function.ip2long
| From: | TeguhIskanto-Kamprettosatyahoo at osu1 dot php dot net | Date: | Fri, 29 Aug 2008 16:53:44 +0000 |
| Subject: | note 85429 added to function.ip2long | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-143987@lists.php.net to get a copy of this message | ||
to Anonymous @ 29-Aug-2008 10:19
If you're speaking about efficiency, there's no absolute right / wrong as it all depends
on the user's needs, specs and requirements.
But from what I'm coming from , this method served me well, I've used this to match 2
network ends of approx 2700++ something unique VRFs (Nortel Shasta) and yes, each VRF is a
virtualized firewall that consists of at least 20 different network objects (some could have couple
of hundreds). Not to mention that these , still have to be compared with another hundreds of
contivity boxes and each box have a range of around 1-600 vpn peers (to add more complexity, each
peer has around 1-50 network ranges).
So, if you do the math, the number of permutations that need to be calculated, is indeed quite
complex. I could get the whole result somewhere in around 50-65 secs tops.
Had I used a php function to crunch those data the result would have been longer.
----
Server IP: 117.104.160.194
Probable Submitter: 60.241.195.155
----
Manual Page -- http://www.php.net/manual/en/function.ip2long.php
Edit -- https://master.php.net/note/edit/85429
Del: integrated -- https://master.php.net/note/delete/85429/integrated
Del: useless -- https://master.php.net/note/delete/85429/useless
Del: bad code -- https://master.php.net/note/delete/85429/bad+code
Del: spam -- https://master.php.net/note/delete/85429/spam
Del: non-english -- https://master.php.net/note/delete/85429/non-english
Del: in docs -- https://master.php.net/note/delete/85429/in+docs
Del: other reasons-- https://master.php.net/note/delete/85429
Reject -- https://master.php.net/note/reject/85429
Search -- https://master.php.net/manage/user-notes.php