Hi Lucas, thanks for your suggestions.

I cannot guarantee the code will be in the same location. I was trying to
avoid NPM because that way I would have to push any change to all apps.
Although in the example I only mentioned three apps I will probalbly work
with more than that. I'm think about 10 different apps (it's an ERP). And
further, I would not be the person responsible for updating the apps and
knowing the infra people I have I will be asking for troubles. :) That's
why I was thinking in something closer to iframe.

Thanks,


--
Allan Ferreira
.NET Software Architect
.NET Senior Consultant
M: +55-31-91459279
E: [email protected] <[email protected]>

On Fri, Aug 12, 2016 at 12:04 PM, 'Lucas Lacroix' via AngularJS <
[email protected]> wrote:

> If your app's code exists in the same location, you can share components
> between the pages without issue, even when using WebPack or other bundling
> software. An alternative to that is to publish the shared components in NPM
> and install them in each appliction - this is the route we are currently
> looking at for projects I am working on.
>
> To share the bearer token between applications, you may be able to use
> SessionStorage or store it on the server as part of the session which can
> be retrieved by an API call to the application server.
>
>
> On Fri, Aug 12, 2016 at 10:48 AM Allan Fagner <[email protected]>
> wrote:
>
>> Hi,
>>
>> I'm having a problem which I'm not sure how to sove. Here is my scenario:
>>
>> Let's assume I have three app, let's call them A, B and C.
>>
>> App A is a ticket traking app. Tickets may be created and routing from
>> any app. So, What I want to do is get parts from App A and display them in
>> apps A, B and C . Another requirement is to use the same bearer toke when
>> doing that, so that the user do not have to login again. Directives are
>> more than welcome if possible to use them.
>>
>> It's more or less like embedding one app into another using IFrame.
>>
>> I have been thinking about possibilities but everything I could came up
>> with falls short in one way or another.
>>
>> Any ideas about how to accomplish that?
>>
>> Thanks
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "AngularJS" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at https://groups.google.com/group/angular.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "AngularJS" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/angular/twngY98Tl9A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/angular.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to