hi nick,
I'm posting this to the list because it's relevant.
> "Init
> The Init layer is prepended to every file served by a
> binarycloud-controlled apache installation tree. Init
> is composed of four subsystems:"
>
> I was wondering how this affected the portability of
> applications written with binary cloud. Portability
> is definitely a concern for most developers these
> days.
Init basically loads up all the system stuff for binarycloud: permissions,
authentication, the constants, etc.
So if you write a bunch of modules that use our code, they will depend on
our code.
Like any other major change, moving a bunch of code _out_ of binarycloud and
fixing all of the dependencies would be a major task, because binarycloud
has a _great_deal_ of code to support your applications, i.e. you write less
coded to begin with, because bc has it already.
I'm not quite sure what you mean by portability - I've assumed you mean
"framework" portability.
As far as platforms go, binarycloud r2 will really be targeted at
unix/linux, not windows - because windows does not offer many of the tools
necessary to support makefiles, etc. - but you can move the code around
without a problem because it's php.
_alex
> =====
> Nick Pavlica
> CTO - Pavlica.com, LLC
> http://www.pavlica.com
>
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
|
