architecture - IBM Worklight session control with back-end server -


got question on ibm worklight server, in advance comments on subject.

workflow:

user --> worklight server --> back-end server

scenario:

(1) designed mobile application ibm worklight studio , deployed worklight server.

(2) must use worklight server first entry point (user authentication ldap via worklight server)

(3) mobile application designed downloading/uploading huge file size (10mb 1gb) backend server behind worklight server (refer workflow pls.)

question(s):

(1) how session sharing can done in between worklight server , back-end server?

(2) if session sharing cannot done, what's safest way mobile application download/upload files back-end server given application , back-end server not know same authenticated transaction skipping worklight server?

(3) did misunderstood worklight server architecture? far know worklight server kind of gateway , presentation layer deploying mobile application framework. heavy , complex computation logic should handled other backend server. long worklight server network io wide enough file transfer, shouldn't problem worklight server act gateway in case. file transfer, shouldn't burden cpu computation in , out user device backend server (worklight middle man).

thank , sorry lengthy question.

(1) how session sharing can done in between worklight server , back-end server?

can make assumption using worklight adapter in order file transfers? in case, "session" between adapter , client created. bit more specific, if have global variable stored in adapter , modify variable based on adapter call client, state of variable maintained upon subsequent requests, , state of variable visible calling client. (just note, not true in clustered environments, client may calling adapters on separate worklight servers)

(2) if session sharing cannot done, what's safest way mobile application download/upload files back-end server given application , back-end server not know same authenticated transaction skipping worklight server?

as stated above, can achieved through adapters. since adapters can protected through authentication, knows client calling through same authenticated transaction.

(3) did misunderstood worklight server architecture? far know worklight server kind of gateway , presentation layer deploying mobile application framework. heavy , complex computation logic should handled other backend server. long worklight server network io wide enough file transfer, shouldn't problem worklight server act gateway in case. file transfer, shouldn't burden cpu computation in , out user device backend server (worklight middle man).

you hit nail on head. haven't done performance testing high amount of computations on worklight server, if being used passthrough should fine. worklight server has been known able process relatively high amount of concurrent adapter calls, believe fine setup.


Comments

Popular posts from this blog

linux - Does gcc have any options to add version info in ELF binary file? -

android - send complex objects as post php java -

charts - What graph/dashboard product is facebook using in Dashboard: PUE & WUE -