S.hostAndPath

[Andreas Joseph Krogh]

Hi all.

 

Any reason why S.hostAndPath doesn't lookup in session when the Req is Empty (like in CometActors)? S.contextPath gets the info from session when Req is Empty, which makes it work in CometActors also. It seems to me like the info building up S.hostAndPath also could exist in session so it could work in CometActors.

 

Thoughts?

 

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

and...@visena.com

www.visena.com

[Antonio Salazar Cardozo]

Do you have a specific place where hostAndPath info would live in the session? Or are you

saying we should start putting it in the session?

Thanks,

Antonio

[Andreas Joseph Krogh]

På onsdag 05. august 2015 kl. 00:10:33, skrev Antonio Salazar Cardozo <savedf...@gmail.com>:

Do you have a specific place where hostAndPath info would live in the session? Or are you

saying we should start putting it in the session?

Thanks,

Antonio

 

I'm saying there's nothing preventing us form storing this information in the session when initing the session, unless I'm missing something.

[Antonio Salazar Cardozo]

Well, path is request-dependent, no? And host could also be request-dependent, if say

you're sending the same cookie via two different URIs (subdomains for example). So I

don't think putting it in the session is a good idea :/

On the other hand, it might be interesting to include the Req or some vestigial version

of it in Listen messages to the CometActor, so it can capture information about a given

long-poll request if needed.

Thanks,

Antonio

[Andreas Joseph Krogh]

På onsdag 05. august 2015 kl. 22:16:31, skrev Antonio Salazar Cardozo <savedf...@gmail.com>:

Well, path is request-dependent, no? And host could also be request-dependent, if say

you're sending the same cookie via two different URIs (subdomains for example). So I

don't think putting it in the session is a good idea :/

 

On the other hand, it might be interesting to include the Req or some vestigial version

of it in Listen messages to the CometActor, so it can capture information about a given

long-poll request if needed.

Thanks,

Antonio

 

I cannot see how the path in question (the context-path that is) request-dependent. Can you explain when this is the case?

The multi-host case (sub-domains) I haven't thought of...

[Antonio Salazar Cardozo]

Just realized hostAndPath is only the context path, not including the path to the template

heh. My bad, that's not a concern :) Context path is actually known by the session, and

fetchable via S.contextPath, which will look up in the session if there is no current request.

Thanks,

Antonio

[Andreas Joseph Krogh]

På torsdag 06. august 2015 kl. 05:00:24, skrev Antonio Salazar Cardozo <savedf...@gmail.com>:

Just realized hostAndPath is only the context path, not including the path to the template

heh. My bad, that's not a concern :) Context path is actually known by the session, and

fetchable via S.contextPath, which will look up in the session if there is no current request.

Thanks,

Antonio

 

I know S.contextPath now works transparently in CometActors as in snippets (didn't before 3.0), but I need S.hostAndPath to work similarly transparent. It's not a blocker for me as it's quite trivial to manually craft such a thing which provides host+port+contextPath for my app.

[Antonio Salazar Cardozo]

Yeah, I'm thinking we can't provide a proper guarantee that host will stay stable

across a session, but we can advise users who need it that they can stash the

hostAndPath in a SessionVar when they need it, which they can then access from

a comet actor.

Thanks,

Antonio