External data validation?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

External data validation?

jewzaam
Administrator
Keeps coming up in discussion.  How could we support doing external validation of a field or set of fields?  My original thought on this was it should be part of a business service or the individual application and therefore was not part of lightblue.  One risk with having a call out to something external is what level of control do we have on that external component?  What if that external component called lightblue?  It could end up being a very costly or even infinite operation.  Yes, things will time out.  Yes, it's on the developer(s) to not do bad things.  But, I have a problem with those points from an enterprise point of view.

Thoughts?
Reply | Threaded
Open this post in threaded view
|

Re: External data validation?

bserdar
What exactly do you mean by "external data validation"? Is it some
facility external clients calls to validate data? Is it getting
metadata about a field so clients can validte? or is it something
else?

We could expose an api that clients can call with data, and we can
return the validation results for it. Is that useful?

On Wed, Oct 29, 2014 at 1:24 PM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> Keeps coming up in discussion.  How could we support doing external
> validation of a field or set of fields?  My original thought on this was it
> should be part of a business service or the individual application and
> therefore was not part of lightblue.  One risk with having a call out to
> something external is what level of control do we have on that external
> component?  What if that external component called lightblue?  It could end
> up being a very costly or even infinite operation.  Yes, things will time
> out.  Yes, it's on the developer(s) to not do bad things.  But, I have a
> problem with those points from an enterprise point of view.
>
> Thoughts?
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/External-data-validation-tp201.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML
Reply | Threaded
Open this post in threaded view
|

Re: External data validation?

jewzaam
Administrator

I mean something with business logic behind it. For example address validation. It's not generic. Each org does it differently if at all. Variations per geography etc...

On Oct 29, 2014 3:56 PM, "bserdar [via lightblue-dev]" <[hidden email]> wrote:
What exactly do you mean by "external data validation"? Is it some
facility external clients calls to validate data? Is it getting
metadata about a field so clients can validte? or is it something
else?

We could expose an api that clients can call with data, and we can
return the validation results for it. Is that useful?

On Wed, Oct 29, 2014 at 1:24 PM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> Keeps coming up in discussion.  How could we support doing external
> validation of a field or set of fields?  My original thought on this was it
> should be part of a business service or the individual application and
> therefore was not part of lightblue.  One risk with having a call out to
> something external is what level of control do we have on that external
> component?  What if that external component called lightblue?  It could end
> up being a very costly or even infinite operation.  Yes, things will time
> out.  Yes, it's on the developer(s) to not do bad things.  But, I have a
> problem with those points from an enterprise point of view.
>
> Thoughts?
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/External-data-validation-tp201.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML



If you reply to this email, your message will be added to the discussion below:
http://dev.forum.lightblue.io/External-data-validation-tp201p202.html
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: External data validation?

bserdar
So in that case, I'd say that's client's responsibility. However, it
is possible to extend the constraints in metadata using custom
extensions, but that requires deployment modifications.

On Wed, Oct 29, 2014 at 1:58 PM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> I mean something with business logic behind it. For example address
> validation. It's not generic. Each org does it differently if at all.
> Variations per geography etc...
>
> On Oct 29, 2014 3:56 PM, "bserdar [via lightblue-dev]" <[hidden email]>
> wrote:
>>
>> What exactly do you mean by "external data validation"? Is it some
>> facility external clients calls to validate data? Is it getting
>> metadata about a field so clients can validte? or is it something
>> else?
>>
>> We could expose an api that clients can call with data, and we can
>> return the validation results for it. Is that useful?
>>
>> On Wed, Oct 29, 2014 at 1:24 PM, jewzaam [via lightblue-dev]
>> <[hidden email]> wrote:
>>
>> > Keeps coming up in discussion.  How could we support doing external
>> > validation of a field or set of fields?  My original thought on this was
>> > it
>> > should be part of a business service or the individual application and
>> > therefore was not part of lightblue.  One risk with having a call out to
>> > something external is what level of control do we have on that external
>> > component?  What if that external component called lightblue?  It could
>> > end
>> > up being a very costly or even infinite operation.  Yes, things will
>> > time
>> > out.  Yes, it's on the developer(s) to not do bad things.  But, I have a
>> > problem with those points from an enterprise point of view.
>> >
>> > Thoughts?
>> >
>> > ________________________________
>> > If you reply to this email, your message will be added to the discussion
>> > below:
>> > http://dev.forum.lightblue.io/External-data-validation-tp201.html
>> > To start a new topic under lightblue-dev, email
>> > [hidden email]
>> > To unsubscribe from lightblue-dev, click here.
>> > NAML
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/External-data-validation-tp201p202.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/External-data-validation-tp201p203.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML
Reply | Threaded
Open this post in threaded view
|

Re: External data validation?

jewzaam
Administrator

Do we allow specifying those extensions in config? If so, could just leave it to that. If the class is on the class path it could be included.

On Oct 29, 2014 4:05 PM, "bserdar [via lightblue-dev]" <[hidden email]> wrote:
So in that case, I'd say that's client's responsibility. However, it
is possible to extend the constraints in metadata using custom
extensions, but that requires deployment modifications.

On Wed, Oct 29, 2014 at 1:58 PM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> I mean something with business logic behind it. For example address
> validation. It's not generic. Each org does it differently if at all.
> Variations per geography etc...
>
> On Oct 29, 2014 3:56 PM, "bserdar [via lightblue-dev]" <[hidden email]>
> wrote:
>>
>> What exactly do you mean by "external data validation"? Is it some
>> facility external clients calls to validate data? Is it getting
>> metadata about a field so clients can validte? or is it something
>> else?
>>
>> We could expose an api that clients can call with data, and we can
>> return the validation results for it. Is that useful?
>>
>> On Wed, Oct 29, 2014 at 1:24 PM, jewzaam [via lightblue-dev]
>> <[hidden email]> wrote:
>>
>> > Keeps coming up in discussion.  How could we support doing external
>> > validation of a field or set of fields?  My original thought on this was
>> > it
>> > should be part of a business service or the individual application and
>> > therefore was not part of lightblue.  One risk with having a call out to
>> > something external is what level of control do we have on that external
>> > component?  What if that external component called lightblue?  It could
>> > end
>> > up being a very costly or even infinite operation.  Yes, things will
>> > time
>> > out.  Yes, it's on the developer(s) to not do bad things.  But, I have a
>> > problem with those points from an enterprise point of view.
>> >
>> > Thoughts?
>> >
>> > ________________________________
>> > If you reply to this email, your message will be added to the discussion
>> > below:
>> > http://dev.forum.lightblue.io/External-data-validation-tp201.html
>> > To start a new topic under lightblue-dev, email
>> > [hidden email]
>> > To unsubscribe from lightblue-dev, click here.
>> > NAML
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/External-data-validation-tp201p202.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/External-data-validation-tp201p203.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML



If you reply to this email, your message will be added to the discussion below:
http://dev.forum.lightblue.io/External-data-validation-tp201p204.html
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: External data validation?

bserdar
No, we don't have them in config. We can extend the config subsystem
for such extensions.

On Wed, Oct 29, 2014 at 6:30 PM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> Do we allow specifying those extensions in config? If so, could just leave
> it to that. If the class is on the class path it could be included.
>
> On Oct 29, 2014 4:05 PM, "bserdar [via lightblue-dev]" <[hidden email]>
> wrote:
>>
>> So in that case, I'd say that's client's responsibility. However, it
>> is possible to extend the constraints in metadata using custom
>> extensions, but that requires deployment modifications.
>>
>> On Wed, Oct 29, 2014 at 1:58 PM, jewzaam [via lightblue-dev]
>> <[hidden email]> wrote:
>>
>> > I mean something with business logic behind it. For example address
>> > validation. It's not generic. Each org does it differently if at all.
>> > Variations per geography etc...
>> >
>> > On Oct 29, 2014 3:56 PM, "bserdar [via lightblue-dev]" <[hidden email]>
>> > wrote:
>> >>
>> >> What exactly do you mean by "external data validation"? Is it some
>> >> facility external clients calls to validate data? Is it getting
>> >> metadata about a field so clients can validte? or is it something
>> >> else?
>> >>
>> >> We could expose an api that clients can call with data, and we can
>> >> return the validation results for it. Is that useful?
>> >>
>> >> On Wed, Oct 29, 2014 at 1:24 PM, jewzaam [via lightblue-dev]
>> >> <[hidden email]> wrote:
>> >>
>> >> > Keeps coming up in discussion.  How could we support doing external
>> >> > validation of a field or set of fields?  My original thought on this
>> >> > was
>> >> > it
>> >> > should be part of a business service or the individual application
>> >> > and
>> >> > therefore was not part of lightblue.  One risk with having a call out
>> >> > to
>> >> > something external is what level of control do we have on that
>> >> > external
>> >> > component?  What if that external component called lightblue?  It
>> >> > could
>> >> > end
>> >> > up being a very costly or even infinite operation.  Yes, things will
>> >> > time
>> >> > out.  Yes, it's on the developer(s) to not do bad things.  But, I
>> >> > have a
>> >> > problem with those points from an enterprise point of view.
>> >> >
>> >> > Thoughts?
>> >> >
>> >> > ________________________________
>> >> > If you reply to this email, your message will be added to the
>> >> > discussion
>> >> > below:
>> >> > http://dev.forum.lightblue.io/External-data-validation-tp201.html
>> >> > To start a new topic under lightblue-dev, email
>> >> > [hidden email]
>> >> > To unsubscribe from lightblue-dev, click here.
>> >> > NAML
>> >>
>> >>
>> >> ________________________________
>> >> If you reply to this email, your message will be added to the
>> >> discussion
>> >> below:
>> >> http://dev.forum.lightblue.io/External-data-validation-tp201p202.html
>> >> To start a new topic under lightblue-dev, email [hidden email]
>> >> To unsubscribe from lightblue-dev, click here.
>> >> NAML
>> >
>> >
>> >
>> > ________________________________
>> > If you reply to this email, your message will be added to the discussion
>> > below:
>> > http://dev.forum.lightblue.io/External-data-validation-tp201p203.html
>> > To start a new topic under lightblue-dev, email
>> > [hidden email]
>> > To unsubscribe from lightblue-dev, click here.
>> > NAML
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/External-data-validation-tp201p204.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/External-data-validation-tp201p207.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML