Options
All
  • Public
  • Public/Protected
  • All
Menu

Class SecureCookie

Object that handle the session

To get stateless server the session is encrypted inside a cookie, so you should not store large amount of data in it If you need big session then i would suggest to use a Memcache store with the user.uuid as a key

It is part of the core framework implementation, you should not rely on any method of this object, as the implementation can change if needed An object session is exposed by the framework, so use this one ( for now it is a SecureCookie.getProxy() but can evolve )

The object use Object.observe if available or try Proxy in other case, so old JS VM won't run it

You cannot store variables starting with _ in the session if you do use them they won't be persist, so it can be used to add some context

Hierarchy

Indexable

[key: string]: any

Object that handle the session

To get stateless server the session is encrypted inside a cookie, so you should not store large amount of data in it If you need big session then i would suggest to use a Memcache store with the user.uuid as a key

It is part of the core framework implementation, you should not rely on any method of this object, as the implementation can change if needed An object session is exposed by the framework, so use this one ( for now it is a SecureCookie.getProxy() but can evolve )

The object use Object.observe if available or try Proxy in other case, so old JS VM won't run it

You cannot store variables starting with _ in the session if you do use them they won't be persist, so it can be used to add some context

Properties

_algo: string
_changed: boolean
_name: string
_raw: string
_secret: string

Methods

  • destroy(): void
  • getProxy(): this
  • getRaw(name: any, cookies: any): string
  • needSave(): boolean
  • sendCookie(ctx: any, name: any, value: any, params: any): void
  • toJSON(): any

Generated using TypeDoc