text:
from typing import Any, AsyncIterable, Callable, Dict, Optional, TypeVar

from azure.core.async_paging import AsyncItemPaged, AsyncList
from azure.core.exceptions import ClientAuthenticationError, HttpResponseError, ResourceExistsError, ResourceNotFoundError, map_error
from azure.core.pipeline import PipelineResponse
from azure.core.pipeline.transport import AsyncHttpResponse
from azure.core.rest import HttpRequest
from azure.core.tracing.decorator import distributed_trace
from azure.core.tracing.decorator_async import distributed_trace_async
from azure.mgmt.core.exceptions import ARMErrorFormat

from ... import models as _models
from ..._vendor import _convert_request
from ...operations._event_hubs_operations import build_create_or_update_authorization_rule_request, build_create_or_update_request, build_delete_authorization_rule_request, build_delete_request, build_get_authorization_rule_request, build_get_request, build_list_authorization_rules_request, build_list_by_namespace_request, build_list_keys_request, build_regenerate_keys_request
T = TypeVar('T')
ClsType = Optional[Callable[[PipelineResponse[HttpRequest, AsyncHttpResponse], T, Dict[str, Any]], Any]]

class EventHubsOperations:
    """EventHubsOperations async operations.

    You should not instantiate this class directly. Instead, you should create a Client instance that
    instantiates it for you and attaches it as an attribute.

    :ivar models: Alias to model classes used in this operation group.
    :type models: ~azure.mgmt.eventhub.v2021_01_01_preview.models
    :param client: Client for service requests.
    :param config: Configuration of service client.
    :param serializer: An object model serializer.
    :param deserializer: An object model deserializer.
    """

    models = _models

    def __init__(self, client, config, serializer, deserializer) -> None:
        self._client = client
        self._serialize = serializer
        self._deserialize = deserializer
        self._config = config

    @distributed_trace
    def list_by_namespace(
        self,
        resource_group_name: str,
        namespace_name: str,
        skip: Optional[int] = None,
        top: Optional[int] = None,
        **kwargs: Any
    ) -> AsyncIterable["_models.EventHubListResult"]:
        """Gets all the Event Hubs in a Namespace.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param skip: Skip is only used if a previous operation returned a partial result. If a previous
         response contains a nextLink element, the value of the nextLink element will include a skip
         parameter that specifies a starting point to use for subsequent calls. Default value is None.
        :type skip: int
        :param top: May be used to limit the number of results to the most recent N usageDetails.
         Default value is None.
        :type top: int
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: An iterator like instance of either EventHubListResult or the result of cls(response)
        :rtype:
         ~azure.core.async_paging.AsyncItemPaged[~azure.mgmt.eventhub.v2021_01_01_preview.models.EventHubListResult]
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        cls = kwargs.pop('cls', None)  # type: ClsType["_models.EventHubListResult"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))
        def prepare_request(next_link=None):
            if not next_link:

                request = build_list_by_namespace_request(
                    resource_group_name=resource_group_name,
                    namespace_name=namespace_name,
                    subscription_id=self._config.subscription_id,
                    api_version=api_version,
                    skip=skip,
                    top=top,
                    template_url=self.list_by_namespace.metadata['url'],
                )
                request = _convert_request(request)
                request.url = self._client.format_url(request.url)

            else:

                request = build_list_by_namespace_request(
                    resource_group_name=resource_group_name,
                    namespace_name=namespace_name,
                    subscription_id=self._config.subscription_id,
                    api_version=api_version,
                    skip=skip,
                    top=top,
                    template_url=next_link,
                )
                request = _convert_request(request)
                request.url = self._client.format_url(request.url)
                request.method = "GET"
            return request

        async def extract_data(pipeline_response):
            deserialized = self._deserialize("EventHubListResult", pipeline_response)
            list_of_elem = deserialized.value
            if cls:
                list_of_elem = cls(list_of_elem)
            return deserialized.next_link or None, AsyncList(list_of_elem)

        async def get_next(next_link=None):
            request = prepare_request(next_link)

            pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
                request,
                stream=False,
                **kwargs
            )
            response = pipeline_response.http_response

            if response.status_code not in [200]:
                map_error(status_code=response.status_code, response=response, error_map=error_map)
                error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
                raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

            return pipeline_response

        return AsyncItemPaged(
            get_next, extract_data
        )
    list_by_namespace.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs"}  # type: ignore

    @distributed_trace_async
    async def create_or_update(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        parameters: "_models.Eventhub",
        **kwargs: Any
    ) -> "_models.Eventhub":
        """Creates or updates a new Event Hub as a nested resource within a Namespace.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :param parameters: Parameters supplied to create an Event Hub resource.
        :type parameters: ~azure.mgmt.eventhub.v2021_01_01_preview.models.Eventhub
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: Eventhub, or the result of cls(response)
        :rtype: ~azure.mgmt.eventhub.v2021_01_01_preview.models.Eventhub
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType["_models.Eventhub"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str
        content_type = kwargs.pop('content_type', "application/json")  # type: Optional[str]

        _json = self._serialize.body(parameters, 'Eventhub')

        request = build_create_or_update_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            content_type=content_type,
            json=_json,
            template_url=self.create_or_update.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        deserialized = self._deserialize('Eventhub', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, {})

        return deserialized

    create_or_update.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}"}  # type: ignore

    @distributed_trace_async
    async def delete(  # pylint: disable=inconsistent-return-statements
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        **kwargs: Any
    ) -> None:
        """Deletes an Event Hub from the specified Namespace and resource group.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: None, or the result of cls(response)
        :rtype: None
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType[None]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        request = build_delete_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            template_url=self.delete.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200, 204]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        if cls:
            return cls(pipeline_response, None, {})

    delete.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}"}  # type: ignore

    @distributed_trace_async
    async def get(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        **kwargs: Any
    ) -> "_models.Eventhub":
        """Gets an Event Hubs description for the specified Event Hub.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: Eventhub, or the result of cls(response)
        :rtype: ~azure.mgmt.eventhub.v2021_01_01_preview.models.Eventhub
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType["_models.Eventhub"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        request = build_get_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            template_url=self.get.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        deserialized = self._deserialize('Eventhub', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, {})

        return deserialized

    get.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}"}  # type: ignore

    @distributed_trace
    def list_authorization_rules(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        **kwargs: Any
    ) -> AsyncIterable["_models.AuthorizationRuleListResult"]:
        """Gets the authorization rules for an Event Hub.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: An iterator like instance of either AuthorizationRuleListResult or the result of
         cls(response)
        :rtype:
         ~azure.core.async_paging.AsyncItemPaged[~azure.mgmt.eventhub.v2021_01_01_preview.models.AuthorizationRuleListResult]
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        cls = kwargs.pop('cls', None)  # type: ClsType["_models.AuthorizationRuleListResult"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))
        def prepare_request(next_link=None):
            if not next_link:

                request = build_list_authorization_rules_request(
                    resource_group_name=resource_group_name,
                    namespace_name=namespace_name,
                    event_hub_name=event_hub_name,
                    subscription_id=self._config.subscription_id,
                    api_version=api_version,
                    template_url=self.list_authorization_rules.metadata['url'],
                )
                request = _convert_request(request)
                request.url = self._client.format_url(request.url)

            else:

                request = build_list_authorization_rules_request(
                    resource_group_name=resource_group_name,
                    namespace_name=namespace_name,
                    event_hub_name=event_hub_name,
                    subscription_id=self._config.subscription_id,
                    api_version=api_version,
                    template_url=next_link,
                )
                request = _convert_request(request)
                request.url = self._client.format_url(request.url)
                request.method = "GET"
            return request

        async def extract_data(pipeline_response):
            deserialized = self._deserialize("AuthorizationRuleListResult", pipeline_response)
            list_of_elem = deserialized.value
            if cls:
                list_of_elem = cls(list_of_elem)
            return deserialized.next_link or None, AsyncList(list_of_elem)

        async def get_next(next_link=None):
            request = prepare_request(next_link)

            pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
                request,
                stream=False,
                **kwargs
            )
            response = pipeline_response.http_response

            if response.status_code not in [200]:
                map_error(status_code=response.status_code, response=response, error_map=error_map)
                error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
                raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

            return pipeline_response

        return AsyncItemPaged(
            get_next, extract_data
        )
    list_authorization_rules.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}/authorizationRules"}  # type: ignore

    @distributed_trace_async
    async def create_or_update_authorization_rule(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        authorization_rule_name: str,
        parameters: "_models.AuthorizationRule",
        **kwargs: Any
    ) -> "_models.AuthorizationRule":
        """Creates or updates an AuthorizationRule for the specified Event Hub. Creation/update of the
        AuthorizationRule will take a few seconds to take effect.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :param authorization_rule_name: The authorization rule name.
        :type authorization_rule_name: str
        :param parameters: The shared access AuthorizationRule.
        :type parameters: ~azure.mgmt.eventhub.v2021_01_01_preview.models.AuthorizationRule
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: AuthorizationRule, or the result of cls(response)
        :rtype: ~azure.mgmt.eventhub.v2021_01_01_preview.models.AuthorizationRule
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType["_models.AuthorizationRule"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str
        content_type = kwargs.pop('content_type', "application/json")  # type: Optional[str]

        _json = self._serialize.body(parameters, 'AuthorizationRule')

        request = build_create_or_update_authorization_rule_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            authorization_rule_name=authorization_rule_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            content_type=content_type,
            json=_json,
            template_url=self.create_or_update_authorization_rule.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        deserialized = self._deserialize('AuthorizationRule', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, {})

        return deserialized

    create_or_update_authorization_rule.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}/authorizationRules/{authorizationRuleName}"}  # type: ignore

    @distributed_trace_async
    async def get_authorization_rule(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        authorization_rule_name: str,
        **kwargs: Any
    ) -> "_models.AuthorizationRule":
        """Gets an AuthorizationRule for an Event Hub by rule name.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :param authorization_rule_name: The authorization rule name.
        :type authorization_rule_name: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: AuthorizationRule, or the result of cls(response)
        :rtype: ~azure.mgmt.eventhub.v2021_01_01_preview.models.AuthorizationRule
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType["_models.AuthorizationRule"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        request = build_get_authorization_rule_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            authorization_rule_name=authorization_rule_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            template_url=self.get_authorization_rule.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        deserialized = self._deserialize('AuthorizationRule', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, {})

        return deserialized

    get_authorization_rule.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}/authorizationRules/{authorizationRuleName}"}  # type: ignore

    @distributed_trace_async
    async def delete_authorization_rule(  # pylint: disable=inconsistent-return-statements
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        authorization_rule_name: str,
        **kwargs: Any
    ) -> None:
        """Deletes an Event Hub AuthorizationRule.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :param authorization_rule_name: The authorization rule name.
        :type authorization_rule_name: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: None, or the result of cls(response)
        :rtype: None
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType[None]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        request = build_delete_authorization_rule_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            authorization_rule_name=authorization_rule_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            template_url=self.delete_authorization_rule.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200, 204]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        if cls:
            return cls(pipeline_response, None, {})

    delete_authorization_rule.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}/authorizationRules/{authorizationRuleName}"}  # type: ignore

    @distributed_trace_async
    async def list_keys(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        authorization_rule_name: str,
        **kwargs: Any
    ) -> "_models.AccessKeys":
        """Gets the ACS and SAS connection strings for the Event Hub.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :param authorization_rule_name: The authorization rule name.
        :type authorization_rule_name: str
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: AccessKeys, or the result of cls(response)
        :rtype: ~azure.mgmt.eventhub.v2021_01_01_preview.models.AccessKeys
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType["_models.AccessKeys"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str

        request = build_list_keys_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            authorization_rule_name=authorization_rule_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            template_url=self.list_keys.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        deserialized = self._deserialize('AccessKeys', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, {})

        return deserialized

    list_keys.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}/authorizationRules/{authorizationRuleName}/listKeys"}  # type: ignore

    @distributed_trace_async
    async def regenerate_keys(
        self,
        resource_group_name: str,
        namespace_name: str,
        event_hub_name: str,
        authorization_rule_name: str,
        parameters: "_models.RegenerateAccessKeyParameters",
        **kwargs: Any
    ) -> "_models.AccessKeys":
        """Regenerates the ACS and SAS connection strings for the Event Hub.

        :param resource_group_name: Name of the resource group within the azure subscription.
        :type resource_group_name: str
        :param namespace_name: The Namespace name.
        :type namespace_name: str
        :param event_hub_name: The Event Hub name.
        :type event_hub_name: str
        :param authorization_rule_name: The authorization rule name.
        :type authorization_rule_name: str
        :param parameters: Parameters supplied to regenerate the AuthorizationRule Keys
         (PrimaryKey/SecondaryKey).
        :type parameters: ~azure.mgmt.eventhub.v2021_01_01_preview.models.RegenerateAccessKeyParameters
        :keyword callable cls: A custom type or function that will be passed the direct response
        :return: AccessKeys, or the result of cls(response)
        :rtype: ~azure.mgmt.eventhub.v2021_01_01_preview.models.AccessKeys
        :raises: ~azure.core.exceptions.HttpResponseError
        """
        cls = kwargs.pop('cls', None)  # type: ClsType["_models.AccessKeys"]
        error_map = {
            401: ClientAuthenticationError, 404: ResourceNotFoundError, 409: ResourceExistsError
        }
        error_map.update(kwargs.pop('error_map', {}))

        api_version = kwargs.pop('api_version', "2021-01-01-preview")  # type: str
        content_type = kwargs.pop('content_type', "application/json")  # type: Optional[str]

        _json = self._serialize.body(parameters, 'RegenerateAccessKeyParameters')

        request = build_regenerate_keys_request(
            resource_group_name=resource_group_name,
            namespace_name=namespace_name,
            event_hub_name=event_hub_name,
            authorization_rule_name=authorization_rule_name,
            subscription_id=self._config.subscription_id,
            api_version=api_version,
            content_type=content_type,
            json=_json,
            template_url=self.regenerate_keys.metadata['url'],
        )
        request = _convert_request(request)
        request.url = self._client.format_url(request.url)

        pipeline_response = await self._client._pipeline.run(  # pylint: disable=protected-access
            request,
            stream=False,
            **kwargs
        )
        response = pipeline_response.http_response

        if response.status_code not in [200]:
            map_error(status_code=response.status_code, response=response, error_map=error_map)
            error = self._deserialize.failsafe_deserialize(_models.ErrorResponse, pipeline_response)
            raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

        deserialized = self._deserialize('AccessKeys', pipeline_response)

        if cls:
            return cls(pipeline_response, deserialized, {})

        return deserialized

    regenerate_keys.metadata = {'url': "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/eventhubs/{eventHubName}/authorizationRules/{authorizationRuleName}/regenerateKeys"}  # type: ignore

redpajama_set_name: RedPajamaGithub


FLUSHING, N.Y. — In a rematch of last year's title game, regular season champion Pratt Institute captured their third straight title and seventh in the last eight years, winning the 2018 Hudson Valley Intercollegiate Athletic Conference women's tennis championship with a 5-0 victory over No. 2 Vaughn College on Sunday afternoon USTA Billie Jean King National Tennis Center.
Top-seeded Pratt (12-2) bypassed No. 4 Berkeley in the semifinals, while Vaughn (3-4) defeated No. 3 New Rochelle (1-6), 5-2, in the other semifinal to set up the title rematch.
In the finals, the Cannoneers swept all three pairs matches with the tandems of Amanda Twu/Melanie Kania and Amy Young/Caroline Madden winning at love, 8-0, at No. 1 and No. 2 doubles. The Warriors managed four games at No. 3 doubles, but Morgan Ferweda/Isabel Campbell prevailed 8-4 for the Cannoneer.
Named Player of the Year at the conclusion of the tournament, Kania was victorious at love at No. 1 singles and Young, named Rookie of the Year, dropped just one game at No. 2 singles to clinch the title with the Cannoneers leading in the remaining four matches.


text:
Endodontic Services
21 Jun What is Endodontic Therapy?
21 Jun Anesthesia
21 Jun Traumatic Dental Injuries
21 Jun Root Canal Retreatment
21 Jun Root Canal Treatment
21 Jun Why South Bay Endodontics?
21 Jun What does an endodontist do?
21 Jun Is a root canal painful?
21 Jun What is Root Canal Therapy
04 Oct Endodontic Updates
In this issue of Update on Endodontics, we've found several sections very interesting....
COVID-19 Patient Disclosures
COVID-19 Emergency Dental Treatment
HIPAA Form
3771 W. 242nd Street
southbayendo@gmail.com
© 2023 South Bay Endodontics. All Rights Reserved. Privacy Policy and Terms & Conditions | Site Map
Nooshin Noghreian D.D.S., M.S., APC
Dr. Noghreian is an Honors graduate of UCLA School of Dentistry. She gained extensive post-graduate training in hospital dentistry as a resident at Veterans Administration Medical Center, Long Beach. After two years in general practice in the Los Angeles area, Dr. Noghreian earned her Master's degree in Endodontics from Loma Linda University. She is a past editor for the Los Angeles Chapter of Alpha Omega Dental Fraternity, Diplomate of the American Board of Endodontics since 2006. Dr. Noghreian served as Board President of the Southern California Academy of Endodontics in 2020.
Ramin Noghreian D.D.S., Inc.
Dr. Noghreian received his DDS degree from the UCLA School of Dentistry. He completed his graduate work at the New York University School of Dentistry with special training in complex endodontic procedures. He has been an instructor at UCLA School of Dentistry, Dept. of Endodontics, and a member of Alpha Omega Dental Fraternity. Dr. Noghreian has served as the President of the Southern California Academy of Endodontics. In 2019, he also served as President of the Board of Directors for the Western Los Angeles Dental Society. In Addition, he has been honored with being a member of the prestigious Academy of General Dentistry, and he has been a Diplomate of the American Board of Endodontics since 2003.
Wayne G. Bemis, D.D.S., was a graduate of the University of Southern California, School of Dentistry and is a Diplomate of the American Board of Endodontics. He practiced Endodontics in Torrance for over 40 years.
Although retired since December 2007, he is still active in the dental community. Dr. Bemis has taught for several years at the University of Southern California, School of Dentistry and is a consultant in Endodontics at the Veteran's Administration Hospital in Long Beach.
He also guest lectures at University of California at Los Angeles and Loma Linda Medical Center.
/g, "%3e" ) .replace( /#/g, "%23" ) .replace( /"/g, "'" ); $img.attr( "src", "data:image/svg+xml;utf8," + newSrc ); } } ); } // Fix starter images. maybeFixSGSrc( $( ".vp-portfolio__items" ) ); // Fix AJAX loaded images. $( document ).on( "addItems.vpf", function ( event, self, $items, removeExisting ) { if ( "vpf" !== event.namespace ) { return; } maybeFixSGSrc( $items ); } ); }(window.jQuery)); Skip to content

redpajama_set_name: RedPajamaCommonCrawl


In November, I attended the Wine Tourism Conference in Portland. While there, I joined a workshop entitled "Social Media for the Wine & Wine Tourism Industries," led by Andrew Healy of 3 Rock Marketing, a Napa-based marketing firm that specializes in online presence and social media. I thought the presentation was great, and was encouraged by his advice, as we use much of those techniques at Trellis Growth Partners for our communications clients. Here are three examples of business practices at Trellis that were also recommended in the workshop. We encourage you to use them as a checklist for your own social media efforts.
Consumers look forward to Facebook page updates, so if yours is rarely updated, chances are your fan base interest will wane, resulting in fewer follows.
At Trellis, we recommend only creating accounts you are confident you will use. You might think Pinterest is great (who doesn't?!), and it can be used for business purposes, but an inactive page with a few photos and a lack of re-pins is not attractive, and can ultimately hurt your image when it comes up on a Google search. So rather than trying to juggle five or ten different "must do" sites, select the one or few that you'll commit to regularly and stick to it. We recommend using Facebook and Twitter, as they are user-friendly and make it easy to communicate with followers.
It's crucial to stay true to your brand messaging when using social media. This is a marketing foundation we develop for clients through a messaging platform process. When interacting with consumers on social media, it is essential to use a consistent and natural brand "voice" to communicate with consumers. What you post and how you phrase it will not be the same as how you post on your personal accounts. If you are having trouble establishing your brand voice, we can help.
For example, Rolling River Sprits' website states, "Rolling River Spirits is a family-owned and operated craft distillery located in Portland, Oregon. The company was founded in 2011 to offer artisan organic spirits made from fresh ingredients." If you go to Rolling River's Facebook page, you will see that the messaging and imagery is consistent. The main brand statements of "artisan, organic spirits," "fresh ingredients," and "family-owned" are emphasized and maintain uniformity.
While setting up Starfield's Facebook page, we wanted to stay anchored to the company's voice. As you can see, both the mission statement and website focus on their family's legacy and commitment to the best vineyard sites.
Maintaining a unified, consistent image and language is an important step to establishing and maintaining trust between your brand and the consumer.
It is important to regularly post to social media, but keep in mind that these are conversational platforms -- it is not enough to focus solely on your page. An easy way to promote your brand, in addition to showing support for others, is to like, comment, and share posts.
In this image, you can see that Mackey Vineyards shared Great Northwest Wine's link e-newsletter announcing Mackey's Concordia as the wine of the week. Here we are both promoting Mackey's press and Great Northwest Wine's page by sharing their link, which shows that Mackey is communicative and informed on social media.
Additionally, you should always respond to followers who comment or ask questions on your accounts. This is a simple way to engage your current fans and appeal to new ones. Failing to do so is the social media equivalent of not returning a phone call.
For example, I posted the below status on McKinley Springs Winery's Facebook page to promote 2014 events. Tim commented that he would be at the June 14 BBQ. I responded, "Can't wait to see you there!" It always feels nice to be recognized, and to a new viewer, it shows that McKinley Springs is engaged with their followers.
One of our primary goals at Trellis is to create brand magnetism for our clients, and social media is just one piece of the puzzle. In my next post, I will explain how to launch a successful social media contest and what it can do for your online presence.


...and this was the third option. While we didn't think that any of them were suitable, this one gave the team pause for thought, and we started to consider the idea of moving in for even more of a close-up, and making a feature of B's hooded head. And that finally led us to the powerful image that ended up on the cover. As you can see, we take our covers VERY seriously -- we don't put anything out there until we're 100% happy with it!


text:
Go to main navigation Go to main content Go to footnote
Logotype Barcelona Macula Foundation, go to home
ca·
Stargardt's disease
Large donations and companies
Bequests and legacies
BMF Club Members
Jordi Monés presents in Israel the latest research on macular degeneration diagnosis and treatment
Dr Jordi Monés, MD, PhD, was the principal speaker at The Annual Israeli Retina Society Meeting. The ophthalmologist and macula and vitreoretinal expert and researcher gave three speeches in which he shared the latest research and developments in macular degeneration with the international medical community specialising in this area.
In one address, Dr Monés set out the developments in research into atrophic AMD by reviewing all the current treatments; from drugs that attempt to halt the disease to the use of the nanopulse laser, drugs aimed at making drusen disappear and, finally, recent results with stem cells. He devoted part of this talk to the research being conducted by the biotech company Cell Cure, which specialises in the development of cell therapies for retinal and neurogenerative diseases and of which he is a scientific advisor. Dr Monés presented results of the implantation and survival of these cells in a group of patients.
In his keynote speech, Dr Monés explained the types of image and optimal protocols that exist for the monitoring of cell therapies for atrophic macular degeneration. He presented the conclusions of two papers in which he took part: the first analyses the advantages and limitations of all the imaging techniques used at present and the second refers to the new definitions and the consensus reached on OCT for the improved definition of atrophy. The latter is serving to create a severity scale for the disease. Specifically, Cell Cure is applying this scale to study the external layers of the retina and analyse the functioning of cells in patients.
In another address, Dr Monés referred to Faricimab, a monoclonal antibody developed by Roche. This has two uses: for diabetic macular oedema and for age-related macular degeneration. Trials, now in phase II, have shown highly promising results both in efficacy and in durability, which will enable the patient to reduce treatment frequency. The Barcelona Macula Foundation, of which Dr Monés is the Director, is currently participating in phase III for both diseases.
Share at Linkedin
Share at Google+
Research is the only solution for the future to fight against blindness
It is only with your help that we can fight against blindness
AMD (Age-related macular degeneration)
Horaci 41-43, Esc. B, 08022 Barcelona, Spain
Last update on 14/01/2020
Corporate-Ethic Line
Pursuant to the Personal Data Protection Act 15/1999 of 13 December, we inform you that the personal data requested will be contained in a file owned by the Barcelona Macula Foundation, registered with the Data Protection Agency. The right to access, rectify, cancel or oppose recognized by the Personal Data Protection Act 15/1999 of 13 December and in the regulations implementing this Act must be exercised in writing, providing a copy of your identity card, to the Barcelona Macula Foundation: Research for Vision, by post (to C/ Horaci, 41-43, Esc B, 08022, Barcelona, Spain) indicating "Data Protection" on the envelope, or by email to info@barcelonamaculafound.org.
This website uses own and third party cookies to give you the best experience when you visit our website. By continuing to use this website, you consent to our use of these cookies.Accept


text:
Chris Pine >
Chris Pine joins Wonder Woman cast
By Bang Showbiz in Movies / TV / Theatre on 29 July 2015
Follow Chris Pine
Chris Pine Gal Gadot
Chris Pine has joined the cast of 'Wonder Woman' in a multi-picture deal that includes sequel options with the DC Movie Universe
Chris Pine has joined the cast of 'Wonder Woman'.
The 'Star Trek' actor has reportedly agreed a multi-picture deal that includes sequel options with the DC Movie Universe to portray Steve Trevor, The Wrap reports.
Plot details for the movie remain under wraps, but Pine's character is expected to be a love interest for Gal Gadot's Diana Prince/ Wonder Woman but will also be given ''plenty of action''.
Earlier this month, the 30-year-old lead actress admitted she expects the movie - which is due for release on June 23, 2017 - won't please them all''.
She said: ''No matter what you do, you can never please them all.
''People will always have something to say because that's the way people are. And it's okay. But for me, it's my job. It's my career. It's my art.''
Gal said she hopes her performance will act as a source of inspiration, but acknowledged it will be a collaborative effort.
She added: ''Whatever I do, I take it very seriously and I do my research and I give it my best. I just want to be able to shine and inspire people.
''And it's not just about me. It's the script and the story and the acting. I hope people are going to love it.''
Patty Jenkins can 'breathe new life' into Star Wars, says Chris Pine
Chris Pine in talks to star in live-action Dungeons and Dragons adaptation
Chris Pine in talks for The Saint reboot
Is Netflix's 'Outlaw King' Starring Chris Pine The New 'Braveheart'?
'Saturday Night Live' Sees Chris Pine Explain That He Is A 'Different Chris'
Hell or High Water Movie Review
Star Trek Beyond Movie Review
Star Trek Beyond Trailer
Hell Or High Water Trailer
The Finest Hours Movie Review
Chris Pine Felt Humbled By His Role In The Finest Hours
Chris Pine Spills On 'Wonder Woman' Role And Reveals Film's WWI Setting
Star Trek Beyond - Teaser Trailer
Chris Pine Signs On As Wonder Woman's Steve Trevor
A Wrinkle in Time Trailer
Time is an extraordinarily complicated thing which does not always behave in the way you...
Wonder Woman Movie Review
Boldly optimistic, this action-packed adventure breathes fresh life into the DC universe with a welcome...
Wonder Woman Trailer
Diana Prince is one of the Amazon warriors of Themyscira, a tribe of women with...
Diana Prince is a goddess and princess of the Amazons. She lives her life surrounded...
Sicario screenwriter Taylor Sheridan delivers another fiercely intelligent, engaging story that maintains high suspense while...
Diana is a princess and one of the best fighters on the island she was...
This is where the Star Trek franchise officially shifts from thoughtful drama into thunderous action....
When the Starship Enterprise finds itself under forceful attack, the crew on board fight to...
Star Trek Beyond is the thirteenth film to be released from the Star Trek franchise...
Hell or High Water is an American heist crime film which follows the journey of...
With its rousing, old-fashioned tone, this fact-based epic is properly thrilling and inspirational, a tale...
Trekkies around the world rejoice! Star Trek Beyond will be upon us next year. The...
The Finest Hours Trailer
It's 1952 and a routine shipment is being undertaken by the crew of an oil...
Z For Zachariah Trailer
After a dramatic cataclysm seemingly destroys all of mankind, a single woman in the deep...


text:
La sociologia fenomenologica si inserisce nella branca dell'interazionismo; nasce agli inizi degli anni cinquanta e si configura come quella disciplina che attribuisce primaria importanza alla struttura intenzionale della coscienza umana al fine di interpretare, comprendere e spiegare l'azione sociale.

Si propone di studiare l'universo del senso comune (cioè i significati attribuiti da una comunità di consociati ai fenomeni e agli oggetti circostanti), che fonda la vita e l'agire quotidiano, al fine di dimostrare che le situazioni sociali sono vissute e costruite dai singoli individui.

Bibliografia
Gattamorta L., Teorie del simbolo. Studio sulla sociologia fenomenologica, Franco Angeli, Milano, 2005.
 Muzzetto L., Segre S. (a cura di), Prospettive sul mondo della vita. Sociologia fenomenologica ed etnometodologia: materiali per un confronto, Franco Angeli, Milano, 2006.  ISBN 884647256X
Crespi F., "La sociologia fenomenologica", Il pensiero sociologico, Il Mulino, 2002, cap. IX. ISBN 978-88-15-08809-3

Voci correlate
Alfred Schütz

Collegamenti esterni
Laura Leonardi, Appunti di Istituzioni di Sociologia, Università di Firenze

Sociologia

redpajama_set_name: RedPajamaWikipedia


text:
Q: Send list of Integer[] from ajax to Spring Controller I' trying to send some data from the frontend to a Controller in Spring. I am able to recover all the data except for the Integer [] objectIds.
This is my ajax function:
           var dataToSend = [{ objectIds: 111 }, { objectIds: 222 }];
           dataToSend = JSON.stringify({ 'objectIds': dataToSend });

           $.ajax({
               type:'POST',
               url:'/sendData',
               data:{'start':start, 'end':end, 'locale':locale, dataToSend},
               async:false,
               dataType: "json",
               success:function(data){}
           });

And this is my Controller function:
    @PostMapping(path="/sendData")
public @ResponseBody String sendData(HttpServletResponse response,
        @RequestParam(required=true, name="start") String start,
        @RequestParam(required=true, name="end") String end,
        @RequestParam(required=true, name="locale") Locale locale,
        @RequestParam(required=false, name="objectIds") Integer[] objectIds) throws DocumentException, IOException {

    //some more code
}

any idea why it's not working??

A: Problem is in the way you are sending JSON
Case 1:  How you are sending
 var dataToSend = [{ objectIds: 111 }, { objectIds: 222 }];
dataToSend = JSON.stringify({ 'objectIds': dataToSend });

var mainJSOn = {
    'start': "start",
    'end': "end",
    'locale': "locale",
    dataToSend
  }
  console.log(JSON.stringify(mainJSOn));

OUTPUT:
   {"start":"start","end":"end","locale":"locale","dataToSend":"{\"objectIds\":[{\"objectIds\":111},{\"objectIds\":222}]}"}

Case 2: How you should actually send
    var dataToSend1 = [{ objectIds: 111 }, { objectIds: 222 }];
    dataToSend1 = JSON.stringify(dataToSend1 );

    var mainJSOn1 = {
        'start': "start",
        'end': "end",
        'locale': "locale",
        'objectIds': dataToSend1
      }

  console.log(JSON.stringify(mainJSOn1));

OUTPUT:
{"start":"start","end":"end","locale":"locale","objectIds":"[{\"objectIds\":111},{\"objectIds\":222}]"}

Look at the Output of Both Cases.
Change your code like done in Case 2
Working Fiddle

A: Your are stringifying the wrong object and burying the key objectIds inside it
Try changing to
var dataToSend = JSON.stringify([{objectIds: 111}, {objectIds: 222}]);

$.ajax({
  type: 'POST',
  url: '/sendData',
  data: {
    'start': start,
    'end': end,
    'locale': locale,
    'objectIds': dataToSend
  },
  // async:false,  // NEVER USE THIS!!!!
  dataType: "json",
  success: function(data) {}
});

redpajama_set_name: RedPajamaStackExchange


text:
Aboutkaplanadmin2018-01-02T16:28:06+00:00
Kaplan Rehabilitation, LLC.
Jerrold L. Kaplan, MDPresident and Medical Director
Dr. Kaplan is the former Vice President and Medical Director of Gaylord Hospital in Wallingford, CT, where he was also the Medical Director of the Industrial Rehabilitation Program. He is an Assistant Clinical Professor of Orthopedics and Rehabilitation at the Yale University School of Medicine, an Assistant Professor in the Department of Traumatology and Emergency Medicine at the University of Connecticut School of Medicine, and a Clinical Adjunct Professor at Quinnipiac University. Dr. Kaplan is Certified by the American Board of Physical Medicine and Rehabilitation.
He received his MD degree from the University of Pennsylvania School of Medicine, completed an Internship at Harvard Medical School, and completed a Physical Medicine and Rehabilitation Residency and Chief Resident year at the Columbia University College of Physicians and Surgeons.
Dr. Kaplan is Certified by the American Board of Physical Medicine & Rehabilitation, member of the American Academy of Physical Medicine and Rehabilitation, and a member of the State of Connecticut Workers' Compensation Commission Medical Advisory Panel, and several other organizations. He is licensed to practice medicine in Connecticut.
Linda F. Pegnataro, OTR/LExecutive Director
Linda is a graduate of the Tufts University Boston School of Occupational Therapy and served as staff Occupational Therapist for both Outpatient and In-Patient OT Services at Gaylord Hospital in Wallingford, CT. Her responsibilities included supervisory capacity for the Acquired Brain Injury Unit, coordination and facilitation of outpatient services for individuals with complex medical needs, psychosocial problems, and workman's compensation or disability injuries.
Concurrent with service at Gaylord Hospital, Linda developed occupational therapy programs in three area skilled nursing facilities in a private practice as part of a multi-disciplinary approach to the rehabilitation process.
Linda had served as Case Manager of the Industrial Rehabilitation program at Gaylord Hospital and is currently the Executive Director of Kaplan Rehabilitation.
Our Special Medical Interests Include:
Musculoskeletal Medicine/Pain Consultation Services
Orthopedic Disorders
Spasticity Management
Return-to-work Services
Rheumatolory
About Physiatry
Physiatry is practiced with patients suffering from disabilities caused by illness, injury or birth defect, which includes but is not limited to spinal cord injuries, traumatic brain injury, stroke, osteoporosis, arthritis, work and sports related injuries.
Physiatry employs medication, as well as orthotics and other non-invasive options. These options include physical therapy, occupational therapy, therapeutic modalities of heat and ice, aqua therapy, nutritional counseling, pain management psychology, trigger point injections, and a host of other options.
By providing an appropriate and fully comprehensive treatment plan, Kaplan Rehabilitation helps patients stay as active as possible at any age. Our broad medical expertise allows us to treat disabling conditions throughout a person's lifetime.
Our practice was established in August 2008 after over 30 years of combined rehabilitation experience, and has been responsible for providing outstanding physical medicine and rehab care. Our specialty is in the area of physiatry. Our many regular patients particularly value our total commitment to their care.
1445 Boston Post Rd, Guilford, CT 06437
PROVIDING COMPREHENSIVE CARE
Rehabilitation Physician Evaluation
Work Injury Consultation & Treatment
Low Back & Neck Injuries
Musculoskeletal Extremity Injuries
Non-Narcotic Pain Treatment & Services
Joint & Trigger Point Injections
© Copyright | Kaplan Rehabilitation LLC | All Rights Reserved
Patients can continue to see Dr. Kaplan at Gaylord Specialty Healthcare
Kaplan Rehabilitation will officially close its doors on December 31, 2020.
Dr. Kaplan is rejoining Gaylord Specialty Healthcare, based in Wallingford, CT, as the Medical Director of Gaylord Outpatient & Workers' Compensation Services. All patients are welcome to continue to see Dr. Kaplan at the Gaylord campus in Wallingford.
Learn more about Gaylord and Dr. Kaplan's new position here.


text:
Executive Compensation after the American Jobs Creation Act
Articles August 2006
The American Jobs Creation Act of 2004 (the "Jobs Act") has radically changed the world of nonqualified deferred compensation in particular and executive compensation in general. The Jobs Act has created a new starting place for structuring nonqualified deferral and retirement plans, but has not necessarily reduced their use or flexibility. In fact, as we begin to understand the new rules more fully, we discover new opportunities for providing executives and employers with desired objectives. Notably, the Jobs Act also impacts many other types of executive compensation arrangements, such as employment agreements and equity, incentive, severance and even some welfare benefit plans in often counterintuitive ways that will continue to plague employers and executives for some time.
Application of New Legislation
The Jobs Act includes a new section in the Internal Revenue Code that specifically deals with deferred compensation plans. This Section, 409A, applies to any plan, agreement, or arrangement that provides for deferral of compensation, other than tax-qualified plans and tax-deferred annuities, IRAs, SEPs, SIMPLEs, Section 457(b) plans, and plans providing for vacation, sick leave, disability, compensatory time, and death payments. Section 409A is not limited to elective non-qualified deferred compensation arrangements but also applies to nonelective supplemental executive retirement plans (SERPs), bonus plans, employment contacts, incentive plans, equity plans and other arrangements that provide for deferred payments as interpreted by the regulations. The application of the new rules to traditional nonqualified deferred compensation arrangements is discussed first, followed by a discussion of its application to other types of executive compensation arrangements.
The new rules establish three new sets of constructive receipt rules. These rules are in addition to all existing rules. In other words, all of the existing rules regarding constructive receipt, economic benefit and assignment of income continue to apply. The likely application of the new rules to tax-exempt organizations which are subject to additional rules under Section 457(f) is also discussed at the end of this article.
Deferral Elections
The new rules address the timing of elections to defer income. These rules are similar to the rules that have historically been used by the IRS as safe harbors for constructive receipt, except that they focus on when "services are performed" rather than on when amounts are "earned." Amounts that are deferred will not be taxed until received if the election to defer is made no later than the end of the calendar year preceding the year in which services are performed. The IRS safe harbor rule allowing elections within 30 days of the participant first becoming eligible to participate in the deferred compensation plan has been retained in the new provisions.
There is also an exception for the deferral of amounts meeting the future regulatory definition of "performance bonus." A performance bonus must be payable over at least 12 months and based on parameters established within the first 90 days of the performance period. Under such circumstances, the election to defer the bonus may be made as late as 6 months before the end of the performance period. Notice 2005-1 and proposed regulations include a temporary definition of "performance based compensation" which requires that the bonus be "contingent on the satisfaction of organizational or individual performance criteria" which are not "substantially certain to be met at the time of the election." Bonuses may include subjective criteria relating to the performance of the participant or a group of participants but the determination of such subjective criteria must not be made by the participant or a family member. The performance compensation does not include any amount that would be paid regardless of performance or based on a level of performance substantially certain to be achieved at the time the criteria is established. Also, performance cannot be simply based on an increase in stock value.
Thus, the new rules follow prior timing of election principles fairly closely but clarify the required timing for bonus deferral elections, which has historically been a very fuzzy area of the law. The new rules codify what was previously the conservative interpretation of the law, but implement a new compromise allowing midyear deferrals for performance based bonuses. It remains to be seen, however, whether final regulations so narrowly define performance based compensation as to cause the cart of the deferral rules to drive the horse of bonus award parameters.
Distribution Elections
The new distribution rules say that compensation or benefits that have been deferred may not be distributed any earlier than the occurrence of any of the following events:
Separation from service (except that key employees of public companies must wait 6 months after separation from service);
Disability of the participant:
For purposes of the statute, a participant is disabled if he (1) is unable to engage in any substantial gainful activity by reason of any medically determined physical or mental impairment that can be expected to result in death or can be expected to last for a continuous period of not less than 12 months, or (2) is, by reason of any medically determinable physical or mental impairment that can be expected to result in death or can be expected to last for a continuous period of not less than 12 months, receiving income replacement benefits for a period of not less than three months under an accident and health policy covering employees of the employer;
Death;
A specified time (or fixed schedule) designated at the date of the deferral, but not at an event;
A change in ownership or effective control of the employer, or in the ownership of a substantial portion of the assets of the employer only as provided by future regulations:
Notice 2005-1 and proposed regulations allow acceleration of payments on a change in control of the employer (or parent entity) and include a fairly broad majority (50%) change of control provision. Acceleration may be automatic under the terms of the plan or at the discretion of the employer but apparently employees may not be given discretion to elect to accelerate distribution at or around the time of the change in control without compliance with the normal change rules which require that the election be made 12 months in advance and delay commencement by at least 5 years - limitations which make little sense in the context of a change in control.
The occurrence of an unforeseeable emergency;
For purposes of the statute, unforeseeable emergency is defined as a severe financial hardship to the Participant resulting from an illness or accident of the Participant, the Participant's spouse, or the Participant's dependent (as defined in Code Section 152(a)), loss of the Participant's property due to casualty, or other similar extraordinary and unforeseeable circumstances arising as a result of events beyond the control of the Participant.
Changes in Distribution Elections
Distribution elections may not be accelerated under any circumstances except as discussed in the next paragraph. A plan may permit participants to change distribution elections to further delay a payment or change the form of a payment, as long as (1) the election does not take effect until at least 12 months after the date on which the election is made, (2) if the election relates to a distribution to be made on separation from service, a specified time or a change of control, then the payment with respect to which the election is made must be deferred for a period of at least 5 years from the date the payment would have otherwise been made, and (3) if the election relates to a specified time, then it must be made at least 12 months before the date of the first scheduled payment.
Acceleration of the time or schedule of any payment of benefits is not permitted unless such an acceleration is permitted by the IRS in regulations. This wording is intended to prevent any type of acceleration, including the use of what have been called "haircut" provisions. A "haircut" is the imposition of a substantial penalty (for example, 10% of the benefit amount) formerly imposed on any acceleration of a distribution. The inclusion of a haircut was based on the premise that the penalty would be sufficient to prevent constructive receipt and taxation of the benefit. This new provision eliminates haircuts and other similar techniques. The new legislation limits not only the employee but also the employer from accelerating distributions under the plan. Thus, plans will no longer be able to allow employers the discretion to accelerate distributions even on termination or restructure of a plan. The legislative history suggests the following exceptions may be implemented through regulatory guidance:
Accelerated distributions beyond the participant's control (e.g., distributions to comply with federal conflict of interest or court orders pursuant to divorce);
Withholding of employment taxes;
Distributions necessary to pay income taxes due to vesting in a section 457(f) plan;
Distributions of minimal amounts for "administrative convenience" (e.g., cash-out amounts); and
Small benefit distributions of $10,000 or less (except for key employees, as discussed above).
Application of New Distribution Rules to Deferred Compensation Plans
The new distribution and change in distribution rules have had the most dramatic effect on the design and structure of nonqualified deferred compensation and retirement plans. Under prior law, participants were generally allowed to change at least the form, and often the commencement date, of retirement benefits up to one year prior to termination of employment. Under the new rules, distributions conditioned on retirement or termination of employment must be elected at the time of the original deferral election and may generally not be changed (even well in advance of retirement) without delaying commencement of the benefits at least 5 years beyond the date of retirement or termination. Because retirees and employers will rarely want to delay commencement of benefits until 5 years after retirement, this limitation effectively prohibits changes to retirement distributions. However, the flexibility lost in retirement elections may be made up to a significant extent by creative use of scheduled date distributions.
Under prior law, scheduled date or in-service distributions were available but conservative advisors did not allow or severely limited the ability to change such distributions. Also, plans generally allowed only one or two scheduled distributions and generally required funds to be paid out in a lump sum or over a fairly short period of time. The new rules specifically allow the change of scheduled distributions (as long as such changes meet the specified change rules) and (so far) do not limit the number of scheduled date elections or changes to such elections which a participant may make either before or after retirement. Thus, a participant who does not know the form in which she would like to receive her retirement benefits need only select a scheduled distribution date at least 5 years in advance of the year in which she wants to begin receiving benefits. Then, 1 year before such scheduled distribution, the participant can make a change election and specify any time and form of payout allowed under the plan, as long as commencement is delayed by at least 5 years. If an employer is willing to offer participants maximum flexibility, a participant might establish 5 scheduled distribution dates in consecutive plan years and then have the ability beginning one year before the first scheduled date to annually decide how much of the amount elected for distribution in the following year to receive and how much to roll another 5 years or more.
The proposed regulations create additional flexibility by providing that plans may allow separate distribution elections for specified payments, accounts or categories of funds as specified in the plan document and change elections may apply separately to each category and even to individual installments if the plan so provides.
The new rules no longer allow unscheduled withdrawal or "call" provisions which previously allowed participants to take unscheduled distributions by payment of a penalty. However, the election of early scheduled distribution dates for multiple accounts which can be rolled forward in 5 year increments allows flexibility to take deferrals out early if it becomes desirable or advisable to do so without penalty.
Thus, while the new rules dramatically change the form which distribution elections may take going forward, they do not necessarily reduce the amount of flexibility which may be provided to participants in connection with the timing of distributions. However, the clear disadvantage of the new rules is the difficulty in communication and administration of such complex alternatives.
Funding Rules
There are two funding rules. The first rule precludes the use of off-shore securitization trusts. An exception is provided if substantially all the services to which the nonqualified deferred compensation relates are performed outside of the jurisdiction. The second rule precludes certain types of financial triggers that are intended to protect the executive in the event of the employer's financial difficulty. Thus, assets cannot be dispersed to a participant based on advance knowledge of changes in a company's financial health. These financial triggers do not include traditional concepts of change in control. Recent pension legislation as added additional limitation to Section 409A on informal funding of nonqualified plans for public companies with under-funded defined benefit plans.
Under the new statutory constructive receipt rules there are onerous penalties for failure to comply. If a plan fails to meet all of the requirements of the rules or does not operate according to the rules, all the compensation for the taxable year and all preceding years is includible in gross income for the taxable year if it is not subject to a substantial risk of forfeiture. Additionally, the taxable amount is increased by interest for the entire time the plan is not in compliance and an excise tax of 20% is then added . The IRS has indicated that these penalties will be imposed individual by individual, so every participant will not be affected by the violation of one participant. The most significant impact of these severe penalties is likely to be the chilling effect on creative plan design.
Reporting and Withholding
The new statutory rules establish new reporting requirements for deferred compensation and withholding requirements for any amounts includible in gross income as a result of new Section 409A. Thus, the deferred compensation amounts will be required to be reported on Form W-2 and Form 1099 when deferred, even though they are not yet taxable. However, as deferred compensation is already reported for Social Security tax purposes, this should not be an onerous additional requirement.
Effective Dates and Transition Rules
The new rules are effective and apply to amounts "deferred" after December 31, 2004. (Earnings on amounts that are grandfathered are also grandfathered and not treated as additional deferrals). However, if plans are "materially modified" after October 3, 2004 (unless the modification is acceptable under IRS guidance), then the grandfather treatment is lost and the amounts are subject to the new rules of Section 409A. Notice 2005-1 and proposed regulations provide transition rules employers until December 31, 2006 to bring plans into compliance with the new rules. Final regulations with more detailed guidance are expected in late October 2006 and will most likely extend this effective date, at least for some purposes. With respect to amounts subject to Section 409A or prior deferrals being brought into compliance with the new Section 409A rules, plans may be amended to provide for new payment elections with respect to amounts deferred prior to the election and the election will not be treated as a change in the form and timing of a payment under Section 409A provided that the plan is amended and the participant makes the election on or before December 31, 2006, as long as the new election does not have the effect of deferring payments scheduled to be made in 2006 or accelerating payments into 2006. Similar rules apply to amending stock option and appreciation rights plans to comply with the new rules. Thus, except with respect to 2006 payments, employers may restructure plans and give employees the right to make new payout elections with respect to existing account balances under the new structure at any time on or before December 31, 2006 (and possibly later depending on effective date provisions of final regulations) .
Grandfathering Rules
The new rules apply to amounts vested or deferred in taxable years beginning after December 31, 2004. With respect to amounts earned in 2004 and payable in 2005, the guidance provides that such amounts will be considered deferred before January 1, 2005 if, by December 31, 2004, (i) the participant has a legally binding right to be paid the amount and (ii) the right to the amount is earned and vested.
The guidance provides that it is not a "material modification" for a participant to exercise discretion over the time and manner of payment of a benefit to the extent such discretion is provided under the terms of the plan as of October 3, 2004. Thus, "call" or "haircut" acceleration provisions should still work in a grandfathered plan . Also, it is not a material modification to change a notional investment measure to, or to add, an investment measure that qualifies as a predetermined actual investment within the meaning of social security tax regulations. The amendment of a plan to bring the plan into compliance with the provisions of Section 409A will not be treated as a material modification.
Application to Other Kinds of Executive Compensation
As indicated in the introduction, these new rules are broad-based and determine the types of plans to which Section 409A will apply. As defined in the statute, Section 409A applies to plans other than qualified plans and bona fide vacation leave, sick leave, compensatory time, disability pay or death benefit plans that have the effect of deferring compensation. For purposes of this definition, the term "qualified plan" includes typical profit sharing and pension plans qualified under Section 401(a), tax-deferred annuities, SEPs, SIMPLES and eligible deferred compensation plans under Section 457(b) (but not ineligible plans under Section 457(f)).
Short-Term Payments Not Deferred Compensation
The proposed regulations issued last September provide that the new rules are not intended to apply to bonus plans or other compensation arrangements where compensation is paid within 2½ months after the close of the taxable year in which the right to the compensation is earned and vested (the "Short Payment Period"). However, to the extent that a compensation arrangement provides for payments beyond this period, it will be subject to the new rules. Proposed regulations provide that if the arrangement does not specify the timing of the payments and payments are in fact made within the Short Payment Period, the payments will not be treated as deferred compensation subject to Section 409A. However, if payments are not made within the Short Payment Period they will be subject to Section 409A and may, therefore, have failed to comply with the requirements and be subject to an excise tax. Thus, it is important that all compensation arrangements now specify the timing of all payments in order to avoid the inadvertent application of Section 409A.
Definition of Substantial Risk of Forfeiture
The Short Payment Period discussed above commences upon the "vesting" of the right to the payment. Vesting occurs when a payment is no longer subject to a "substantial risk of forfeiture." The proposed regulations include a new definition of "substantial risk of forfeiture" and provide that compensation is subject to a substantial risk of forfeiture if entitlement to the amount is conditioned on the performance of substantial future services by any person or the occurrence of a condition related to a purpose of the compensation, and the possibility of forfeiture is substantial. Interestingly, the new rules provide that substantial risks of forfeiture added after the beginning of the service period to which the compensation relates are disregarded for purposes of determining whether the compensation is subject to a substantial risk of forfeiture (i.e. rolling risks of forfeiture will not work). In addition, unlike the substantial risk of forfeiture standard that applies under Section 83, an amount is not subject to a substantial risk of forfeiture under Section 409A merely because the right to the amount is conditioned, directly or indirectly, upon the refraining from performance of services. Thus, non-competes will not constitute a substantial risk of forfeiture under the Section 409A definition. Proposed regulations also provide that an amount will not be considered subject to a substantial risk of forfeiture beyond the date or time at which the recipient otherwise could have elected to receive the amount of compensation, unless the amount subject to a substantial risk of forfeiture (ignoring earnings) is materially greater than the amount the recipient could have elected to receive. As a result, a salary deferral generally may not be made subject to a substantial risk of forfeiture. Proposed regulations also question whether amounts that may be paid on termination "for good reason" are subject to a substantial risk of forfeiture. As a result, many severance payments may be subject to Section 409A. Finally, Notice 2005-1 and proposed regulations include guidance regarding substantial risks of forfeiture when the service provider has a significant ownership interest in the service recipient.
Section 409A should not apply to annual bonus plans to the extent that bonus payments are made within the Short Payment Period. However, it would be safest to specify this timing in bonus plan documents or an employment agreement in order to avoid the inadvertent application of Section 409A if bonus payments are not made by this date. To the extent that a multi-year bonus plan or other arrangement provides for the payment of compensation beyond the Short Payment Period, it will be subject to the new rules. Also, to the extent that voluntary deferral plans allow the deferral of bonus amounts, it may be necessary to make sure the bonus plans comply with the definition of "performance based compensation" under the new rules to enable the deferral of bonuses 6 months before completion of the performance period.
Application to Employment Agreement
Section 409A may apply to many types of payments under an employment or consulting agreement. It is, thus, important to specify the timing of each type of payment to either exclude it from application of Section 409A as within the Short Payment Period or comply with Section 409A specified payment date requirements. Application of the six-month delay requirement may be avoided by specifying payments to be made within the Short Payment Period. The timing of severance payments should no longer be in the discretion of the employer, and care should be taken to comply with Section 409A if severance is payable upon termination for good reason. While the continuation of some forms of benefits after termination of employment will not be considered deferred compensation, proposed regulations are less than perfectly clear about what type of benefits may be extended, and for how long, without becoming subject to application of Section 409A. If there is any possibility of payments being made or benefits provided outside the Short Payment Period, appropriate Section 409A language should be included in the employment agreement to provide for application of the six-month rule on termination of employment of a key employee, and to specify that the parties shall not have discretion to accelerate or change the timing of payments in violation of Section 409A.
Equity-Based Compensation
Notice 2005-1 and proposed regulations make clear that the grant of a stock option, SAR, or other equity-based compensation may provide for deferral of compensation that is subject to the new rules subject to the following limitations:
Stock Options:
The grant of incentive stock options under Section 422 and the grant of an option under an employee stock purchase plan under Section 423 do not constitute deferrals of compensation under Section 409A. All other options to purchase stock of the service recipient will not constitute deferrals of compensation only if all of the following requirements are satisfied: (A) the exercise price is not less than the fair market value of the underlying stock on the grant date, (B) the receipt, transfer or exercise of the option is subject to taxation under Code Section 83, and (3) the option does not include any feature for the deferral of compensation other than the deferral of recognition of income until the later of exercise or disposition of the option. For purposes of determining the fair market value of stock at the date of grant, the proposed regulations include valuation rules for public companies and provide that, for non-public entities, any reasonable valuation method may be used until further guidance is issued. Proposed regulations further specify that the stock must be common stock of the service recipient or its parent.
Stock Appreciation Rights:
Proposed regulations provide that the grant of a SAR for the stock of the service recipient does not constitute a deferral of compensation if the SAR exercise price is not less than the fair market value of the underlying stock on the date the right is granted, and the right does not include any feature for the deferral of compensation other than the deferral of recognition of income until the exercise of the right.
Restricted Property:
Proposed regulations provide that there is no deferral of compensation if a service provider receives property merely because the value of the property is not includible in income (under Section 83) in the year of receipt by reason of the property being nontransferable and subject to a substantial risk of forfeiture, or is includible in income (under Section 83) solely due to a valid election under Section 83(b). However, the new rules do apply to the receipt of a legally binding right to receive property (whether or not the property is restricted property) in a future year. Thus, restricted stock units or phantom stock will generally be subject to the new rules, while restricted stock will not (assuming the requirements prescribed above are satisfied).
Partnership Interests:
Notice 2005-1 and proposed regulations provide that while Section 409A will apply to compensation deferral arrangements between a partner and a partnership, until further guidance is issued, an issuance of or grant of an option to purchase a partnership interest in connection with the performance of services will be treated in the same manner as an issuance or option grant of stock.
Split Dollar Life Insurance
Proposed regulations indicate that collateral assignment split dollar life insurance arrangements and, under some circumstances, even endorsement structure split dollar arrangements may be subject to Section 409A. Special guidance is expected to be issued later this year to address the application of Section 409A in this context and the interaction between the transition rules under Section 409A and the grandfathering rules under the new split dollar regulations which were effective September 17, 2003.
Likely Application to Tax-Exempt Organizations
Tax-exempt organizations are subject to special deferred compensation rules under Section 457. Section 457(b) eligible plans are specifically exempted and only Section 457(f) plans are subject to the new rules. Because Section 457(f) plans generally do not involve voluntary deferrals of compensation, they will be subject to the new timing of deferral election rules. Also, Section 457(f) plans generally cliff vest benefits on retirement and do not offer any choices regarding the time and form of distribution nor any opportunity to accelerate distributions, except on death or disability. Thus the new rules limiting forms of distribution, acceleration and changes in distributions should not affect Section 457(f) plans significantly.
Benefits payable under Section 457(f) plans are often conditioned upon a "substantial risk of forfeiture." Thus, the new definition of "substantial risk of forfeiture" which excludes rolling risks of forfeiture and noncompete provisions, if applied to Section 457, may significantly impact Section 457(f) plans.
The new rules are likely to require certain definitional changes such as the definition of disability under the plan. They may also require amendment of termination provisions which allow employers to liquidate the plan. Also, the new reporting requirements will apply to Section 457(f) plans. The new rules may also have adverse tax consequences for other plans that are not covered by Section 457(f), such as severance plans, split dollar, SAR and discounted option plans that may be sponsored by tax-exempt organizations.
This Report is a publication of Loeb & Loeb and is intended to provide clients and friends with information on recent legal developments which may warrant your attention. This Report should not be construed as legal advice or an opinion on specific situations. For more information, please contact Marla Aspinwall, Chair of Loeb's Executive Compensation Group.
Circular 230 Disclosure: To assure compliance with Treasury Department rules governing tax practice, we inform you that any advice contained herein (including any attachments) (1) was not written and is not intended to be used, and cannot be used, for the purpose of avoiding any federal tax penalty that may be imposed on the taxpayer, and (2) may not be used in connection with promoting, marketing, or recommending to another person any transaction or matter addressed herein.
Executive Compensation & Employee Benefits
Client Alerts/Reports Income Tax Provisions of the Tax and Jobs Act
Client Alerts/Reports Highlights of Senate Tax Bill
Articles SEC Proposes Compensation Clawback Rules
Articles Nonqualified Deferred Compensation Section 409A Compliance


For the worship team, Christmas is both a time of celebration and dread. Celebration, because of the wonderful theme of Christ's incarnation and the manifestation of God's salvation plan for all mankind; and roast turkey and festive carol-singing. Because everyone loves to sing carols. But dread, because whilst everyone loves to sing carols, the worship team usually hates to play them.
In the context of a Sunday service, a carols service always presents dual challenges. The first is that singing carols can devolve into mere singalong without the elements of worship engagement and verticality. The second is that there are so many arrangements for carols that there are no reference points for church musicians, unless you write your own arrangements.
Yesterday, we had the first of a series of Christmas-themed services at Faith Community Church. And what a challenge it was!
Three weeks earlier, my music director (the ever hard-working and talented Lukey Luke) sent me a youtube link to a Lincoln Brewster-led Christmas service. It was such a fresh guitar-driven sound (yet reminiscent of Christmas because of the bells and tambourine elements). So we decided to style a set around this idea, including refreshing an old song (Graham Kendrick's "The Servant King" which contains such powerful lyrics).
I also wanted to get Diana Wee to start leading worship with me on the team and we were on the same page when we both decided that "This is our God" would be a great focus song.
So, after fashioning the set, we were all ready to go and there was quite a sense of excitement within the team. However, there were no illusions about how easy it was to play the set – it was going to be challenging.
Rehearsal on Saturday afternoon was tough. We went from 4.00 pm to 7.30 pm. In the words of Caleb our drummer, this was "the most difficult set yet". He wasn't kidding (and Caleb had to play for a Hillsong worship leader just a couple of months earlier). I was starting to wonder if we bit of more than we could chew on top of battling a stomach bug. And I got a little worried the set was going to be too long.
But something miraculous happened when we reconvened on Sunday morning. Suddenly there was a renewed sense of energy and we started flowing well. I suspect the team went home and put some more work into the set and then rested well. And as I timed our run-through, it came to a well-timed 26 minutes!
As we played through the service, there was a growing sense that we were going to musically nail it. But not only that, it felt like we had entered into a divine flow and there was a real sense of God's presence. By the end of it, if felt like our team had just broken through new frontiers of musical creativity. Carols might never be the same again!
And here's a recording of it by our amazing sound guy, Senny.
I want to take this opportunity to thank the band for all their hard work musically and their continued pursuit of God's presence. Playing with you guys have been an amazing honour. May God continue to grow us together and take to new realms of His glory. The best is yet to come!


text:
The Box Office is open from 12:00 till 20:30 (will open in 04:35).
Cinema and More
Kinodvor's Programme for Schools
Film Under the Stars
Halloween Horror Marathon
Open-air Cinema at Congress Square
Rendez-vous with Coffee and Talk
3. Kinotrip
The Breadwinner The Breadwinner
Nora Twomey / Ireland, Canada, Luxembourg / 2017 / 93 min / English
Let film take you to faraway lands on the wings of stories!
IMDb Official website
Through the eyes of a brave girl named Parvana, we get to know a world where freedom and security are no longer a given. When her father is imprisoned by the Taliban, Paravana has to provide for her family and so, dressed as a boy, she hits the turbulent streets of Afghanistan. But the freedom enabled by the new disguise also brings numerous dangers, which she faces while attempting to save her father.
Parvana is the latest animated film by the renowned studio Cartoon Saloon (The Secret of Kells, Song of the Sea) and this year's Oscar nominee for best animated film, which paints an unforgettable story about great courage and an incredible power of the imagination.
Kinodvor. Newsletter.
Join our mailing list and receive details of upcoming films and events!
Kino Babies
Alcarràs Alcarràs
Carla Simón
Wednesday, 01. 02. 2023 / 13:00 / Main Hall
The Catalonian director shines light on the joys and troubles of a family of beach farmers facing an uncertain future. Winner of the Golden Bear at the Berlinale.
Corsage Corsage
Marie Kreutzer
A new look at the life of the beloved Empress Elisabeth of Austria. At 75th Cannes, actress Vicky Krieps won the Un Certain Regard Best Performance Prize for her portrayal of the idolized Empress Sissi.
All the Beauty and the Bloodshed All the Beauty and the Bloodshed
Wednesday, 01. 02. 2023 / 17:00 / Small Hall
This deeply personal yet at the same time distinctly political documentary by Laura Poitras (Citizenfour) explores the inextricable link between the activism and the life and artistic work of Nan Goldin, one of the world's most prominent photographers. A Golden Lion for the best film at last year's Venice Film Festival.
The Bookshop
The Café
Kinodvor Public Institution is founded by:
All rights reserved © Kinodvor | Authors | Legal Notice


text:
Something weird is happening with Telltale games on Steam
Eric Abent - Nov 15, 2018, 1:15 pm CST
It looks like the end of Telltale Games may nearly be upon us. A new report today claims that Telltale is in the process of winding down for good, with liquidation of the company's assets underway. On top of that, some of Telltale's games have started disappearing from Steam, leaving us wondering if more will soon follow.
It certainly sounds like Telltale's days are numbered, but for the moment at least, most of its extensive library is still available on Steam. Series such as Jurassic Park, Back to the Future, and Tales From Monkey Island have been delisted, and though advertisements for the various games based on The Walking Dead still exist on Telltale's developer page, you can't actually buy any of them.
The reason for these delistings is unknown. It's possible that these games have been removed from Steam because of licensing, but it's also worth pointing out that some of Telltale's other licensed games – Game of Thrones, Batman, and Guardians of the Galaxy specifically – are still up. At the moment, we're wondering if these delisted games will return at some point in the future or if more games will follow suit.
Earlier today, GameDaily published an extensive report that claims Telltale is currently liquidating its assets through a process called assignment for the benefit of creditors. Though assignment is different from bankruptcy, the outlook is similar for Telltale: the company is probably in its final days, with a former employee telling GameDaily that post-employment health insurance is set to run out at the end of the month.
Back in September, Telltale laid off 250 workers and said at the time that a skeleton crew of 25 would continue working with the company. Telltale's CEO, Pete Hawley, said then that it wouldn't be shutting down, but today's report paints a very different picture for the company.
Those who were worried that this meant a premature end for the final season of The Walking Dead can breathe something of a sigh of relief, as Telltale announced a partnership with Skybound last month to get the season finished. Whether or not that deal will change as Telltale moves through assignment is unknown, but until we hear otherwise, it's probably best to assume that development is proceeding as planned.
So, if you've been thinking about grabbing some of Telltale's titles, it seems that now is the time. We'll be keeping an eye on Telltale as we move through the coming weeks, and we'll update you if any new information surfaces. Stay tuned.
Telltale's 'Guardians of the Galaxy' series arrives this spring
Telltale's 'Guardians of the Galaxy' game arrives on Android, iOS and consoles
Nintendo Switch is getting Batman and Guardians Of The Galaxy from Telltale
Topics BusinessSteamTelltale Games