Yes, I believe the original use case was done for circles but i think that
too restrictive.

Thanks
Suho

On Wed, Oct 22, 2014 at 1:20 PM, Damith Wickramasinghe <dami...@wso2.com>
wrote:

> Hi,
>
> I thought the use case as the below image shown. I will add the necessary.
> Thank you.
>
> Regards,
> Damith.
>
>
> On Wed, Oct 22, 2014 at 7:46 PM, Sriskandarajah Suhothayan <s...@wso2.com>
> wrote:
>
>> The stationary alert need not only be defined on a  stationery circle
>> but the user should also be able to define a polygon instead. So make it
>> as:
>>
>> An area where the the stationary alert is valid (here we can pass the
>> geo-fence ), and then the time period.
>>
>> Suho
>>
>> On Wed, Oct 22, 2014 at 9:30 AM, Damith Wickramasinghe <dami...@wso2.com>
>> wrote:
>>
>>> Attaching the document.
>>>
>>> On Wed, Oct 22, 2014 at 6:50 PM, Damith Wickramasinghe <dami...@wso2.com
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> Following is the Architecture for Stationery alert requirement.
>>>>
>>>> Use case: An alert should be generated if an object stays in a specific
>>>> place for some specific time
>>>>
>>>> User will be providing the stationery position, its radius and the
>>>> time. Then an alert will be given  if the object satisfies following two
>>>> conditions.
>>>>
>>>> 1.Object should come into the stationery circle, which is created using
>>>> the radius user provided.
>>>> 2.Object should be in the circle for a specific time which user
>>>> provided.
>>>>
>>>>  Please find below the link for the Architecture.
>>>>
>>>> [1] Architecture
>>>> <https://docs.google.com/a/wso2.com/drawings/d/1X1LE8qjbXCvLmqHVrFoAFkTBdNHxDCiUrQd_FwfEDMA/edit?usp=sharing>
>>>>
>>>>
>>>> Best Regards,
>>>> Damith Wickramasinghe.
>>>>
>>>> --
>>>> Software Engineer
>>>> WSO2 Inc.; http://wso2.com
>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
>>>> lean.enterprise.middleware
>>>>
>>>> mobile: *+94728671315 <%2B94728671315>*
>>>>
>>>>
>>>
>>>
>>> --
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94728671315 <%2B94728671315>*
>>>
>>>
>>
>>
>> --
>>
>> *S. Suhothayan*
>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>>  *WSO2 Inc. *http://wso2.com
>> * <http://wso2.com/>*
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>>
>
>
>
> --
> Software Engineer
> WSO2 Inc.; http://wso2.com
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
> lean.enterprise.middleware
>
> mobile: *+94728671315 <%2B94728671315>*
>
>


-- 

*S. Suhothayan*
Technical Lead & Team Lead of WSO2 Complex Event Processor
 *WSO2 Inc. *http://wso2.com
* <http://wso2.com/>*
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
<http://suhothayan.blogspot.com/>twitter: http://twitter.com/suhothayan
<http://twitter.com/suhothayan> | linked-in:
http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to