|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SOPHT.net vs. LOCAL.net A frequent and very understandable question is that
regarding the relative merits of SOPHT.net & LOCAL.net. From the key
standpoint of our intraG application technology pharOS, the differences will
only become significant when pharOS/12 (P12) is launched as P12 is a fully
web aware product built using the Microsoft .NET architecture. P12 will be
highly integrated with our eBroadcast technology iSAS and this means that P12
will be available for LOCAL.net as a series of plug in components for
intranets whilst under SOPHT.net it will be available as a fully featured
remote broadcast service managed & maintained by SOPHTLOGIC. For customers whose preference is locally hosted
solutions we would therefore recommend the eSAT technology track of intraG
whereby a fully configured iSAS satellite installation is deployed which may
then deliver a local SOPHT.net service. However, those various scenarios are only relevant to
P12. Under the current pharOS/7 & pharOS/10 technology tracks LOCAL.net
P10 is comparable with the SOPHT.net P10i and P10e tracks. The only
significant difference between LOCAL.net and SOPHT.net in the P10 scenario is
that SOPHT.net has a wider eBroadcast Channel Spectrum due to the additional
broadcast capabilities which iSAS delivers. The typical SOPHT.net and
LOCAL.net eBroadcast spectrums are shown below. intraGlobal
eBroadcast Channels
Items marked * are channels which are supported as
part of a licensed LOCAL.net eBroadcast facility. However, day to day support
and delivery for those components is the responsibility of the customer
deploying applications & data services via the LOCAL.net signal. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||