Thread: [binarycloud-dev] revised entity def format...

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

added entity:desc, and <encrypt> to field defs.

any other comments?

best,

-alex

QWxleCBCbGFjayB3cml0ZXM6DQogPiBhZGRlZCBlbnRpdHk6ZGVzYywgYW5kIDxlbmNyeXB0
PiB0byBmaWVsZCBkZWZzLg0KID4gDQogPiBhbnkgb3RoZXIgY29tbWVudHM/DQogPiANCiA+
IGJlc3QsDQogPiANCiA+IC1hbGV4DQogPiANCiA+IDw/cGhwDSRlbnRpdHkgPT4gYXJyYXko
DSAgICAnbmFtZScgPT4gJ2Z1cmJlZXMnLA0gICAgJ2Rlc2MnID0+DQonVGhpcyBpcyBhbiBl
eGFtcGxlIGVudGl0eSB1c2VkIGZvciBkZXZlbG9wbWVudC4nLA0gICAgJ21hbmFnZXInID0+
DQonRnVyYmVlc01hbmFnZXInLA0gICAgJ2RhdGFiYXNlJyA9PiBhcnJheSgNICAgICAgICAn
bmFtZScgPT4NCi4uLmV0Yy4uLg0KDQphbGV4LCBpbiB0aGUgZnV0dXJlLCBpcyBpdCBwb3Nz
aWJsZSBmb3IgeW91IHRvIHBhc3RlIHRoaXMgYXMgdGV4dCB3aXRoDQpzdGFuZGFyZCB1bml4
IExGcyA/ICBsaW5lIHdyYXBwaW5nIGlzIGp1c3Qgc2hvdCB3aXRoIHRoZXNlIHBhc3RlcyBm
cm9tDQphIE1hYy4uLg0KDQp0aGFua3MuDQoNCi0tIA0KUmVnYXJkcywNCk1hcmt1cyBLcnVt
bWVuYWNrZXI=

DQpXaG9hLi4gaGFkIHRvIGFzay4gIFdoYXQgaGFwcGVuZWQgaGVyZT8gIFJlbWluZHMgbWUg
b2YgdGhlIG9sZA0KKysrQVRI21N2q8nJaLnf3Xr5c1NYpyxYrLW4p2q8Py1OTyBDQVJSSUVS
DQoNCj5LcnVtbWVuYWNrZXL//////////////////////////////////////////////9tT
dqvJyWi53916+XNTWKcsWKy1uKdqvD8tPz/916/+WKy2z+yi6tx5+is/7+d62G22P///+WKy
2/+yP6tx5+iuB/8/638tKy2z+WKy2Kd+P9tTdqvJyWi5390NCg==

V2hvYSwgd2hhdCBoYXBwZW5lZD8gIFJlbWluZHMgbWUgb2YgdGhlIG9sZDoNCisrK0FUSDDJ
yWi53916+XNTWKcsWKy1uKdqvD8tPz/9Tk8gQ0FSUklFUg0KDQoNCj4gTWFya3VzIEtydW1t
ZW5hY2tlcv//////////////////////////////////////////////21N2q8nJaLnf3Xr5
c1NYpyxYrLW4p2q8Py0/P/3Xr/5YrLbP7KLq3Hn6Kz/v53rYbbY////5YrLb/7I/q3Hn6K4H
/z/rfy0rLbP5YrLYp34/21N2q8nJaLnf3Q0K

Hi,

hehe, oh I have a old courier modem somewhere, I think i'll connect it just
to hear the groovy sound  again ;-)

Andi

>Whoa, what happened?  Reminds me of the old:
>+++ATH0ÉÉh¹ßÝzùsSX§,X¬µ¸§j¼?-??ýNO CARRIER
>
>
>> Markus
>KrummenackerÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÛSv«ÉÉh¹ßÝzùsSX§,X¬µ
>¸§j¼?-??ý×¯þX¬¶Ïì¢êÜyú+?ïçzØm¶?ÿÿùb²Ûÿ²?«qçè®ÿ?ë-+-³ùb²Ø§~?ÛSv«ÉÉh¹ßÝ
>n)Ú¯'%¢ç]zùX§X¬µ¸§j¼uëåËl²«qçè®§zØm¶?þX¬¶Ë(º·~àzwþX¬¶
>ÏåËbú?n)Ú¯'%¢ç]

> Alex Black writes:
>> added entity:desc, and <encrypt> to field defs.
>> 
>> any other comments?
>> 
>> best,
>> 
>> -alex
>> 
>> <?php
> $entity => array(
>   'name' => 'furbees',
>   'desc' =>
> 'This is an example entity used for development.',
>   'manager' =>
> 'FurbeesManager',
>   'database' => array(
>       'name' =>
> ...etc...
> 
> alex, in the future, is it possible for you to paste this as text with
> standard unix LFs ?  line wrapping is just shot with these pastes from
> a Mac...

In CVS, the files are fine... unfortunately Entourage (the client I use)
doesn't know about anything but mac linebreaks.

_a

On Tue, 25 Sep 2001, Alex Black wrote:

> added .. <encrypt> to field defs.
> 

Wouldn't this be better accomplished with a user-definable field-type with an
associated I/O class..having a tag called "encrypt" seems too simplistic to
really provide any meaningful encryption service..

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

> Wouldn't this be better accomplished with a user-definable field-type with an
> associated I/O class..having a tag called "encrypt" seems too simplistic to
> really provide any meaningful encryption service..

For example: we'll have systeic control over encryption settings, but I
think it's safe to assume that a developer would want to use the same key
length and settings for all the fields (as it would be a nightmare to
maintain a key per field, etc)

in the entity definition, encryption is as simple as "encrypt" ... elsewhere
we'll have very fine control over what exactly happens as a result.

...

We will have an I/O class if I read manuel's previous message correctly, and
that will load a configuration file. probably called conf/Encryption.php or
something :)

does that make sense or did I miss your point?

_alex

>> Wouldn't this be better accomplished with a user-definable field-type with an
>> associated I/O class..having a tag called "encrypt" seems too simplistic to
>> really provide any meaningful encryption service..
> 
> For example: we'll have systeic

heh, that is not a word. somehow "systemic" became "systeic"

_a

On Tue, 25 Sep 2001, Alex Black wrote:

> > Wouldn't this be better accomplished with a user-definable field-type with an
> > associated I/O class..having a tag called "encrypt" seems too simplistic to
> > really provide any meaningful encryption service..
> 
> For example: we'll have systeic control over encryption settings, but I
> think it's safe to assume that a developer would want to use the same key
> length and settings for all the fields (as it would be a nightmare to
> maintain a key per field, etc)
> 
> in the entity definition, encryption is as simple as "encrypt" ... elsewhere
> we'll have very fine control over what exactly happens as a result.
> 

Cool, as long as using that tag doesn't mean you get shitty 56bit encryption
with a static salt :)

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

> On Tue, 25 Sep 2001, Alex Black wrote:
> 
>>> Wouldn't this be better accomplished with a user-definable field-type with
>>> an
>>> associated I/O class..having a tag called "encrypt" seems too simplistic to
>>> really provide any meaningful encryption service..
>> 
>> For example: we'll have systeic control over encryption settings, but I
>> think it's safe to assume that a developer would want to use the same key
>> length and settings for all the fields (as it would be a nightmare to
>> maintain a key per field, etc)
>> 
>> in the entity definition, encryption is as simple as "encrypt" ... elsewhere
>> we'll have very fine control over what exactly happens as a result.
>> 
> 
> Cool, as long as using that tag doesn't mean you get shitty 56bit encryption
> with a static salt :)

em, no.

hehe.

yes, it's encryption for three-year-olds!

:)

_a