Originally posted by Joseph Zhou:
Sorry, something unclear my last post. the login still need to have some implementation becuase I assume the FFMS has single sign on. The followed question is for HTML solution: is the transaction broken/disconnected?
Originally posted by Ramon Gill:
Hi,
IMO you can change/create an interface without changing the system. With the right assumptions of course.
Ray
Originally posted by Ramon Gill:
Frequent Flyer System.
Ray
Originally posted by Ramon Gill:
Hi Luca,
From looking at other threads it seems you are pretty keen to get some answers ... so heres my views ...
1. replace
2. replace. You're right about FFN.
3. The assigment says the FFS must remain. It doesn't mention how you interface with it. That's up to you.
Ray
Originally posted by Sudhansu Pati:
I have understood what you say but there is a problem: if I write a java
application to access the content of the FFM this means that I can access to the Oracle database of FFM without going on using the web interface of FFM written in perl/cgi/html of FFM. Are you agree?
------------------------------
I don't agree. FBN requires to use the FFM system as it is. You can't rewrite it.
In fact if I give to the travel agents this new java application to access the Oracle DB of FFM for what reason they should go on using the old web interface? This would make sense only if my java application connects to the FFM using the old web interface: this means to use a screen-scraper solution but in this way I can't distinguish the data type being retrieved and this is what I absolutely need (for example, as you say, to get the points redeemed)!! Can you help me in this sense? I am driving crazy to understand this point! Thanks a lot in advance!
Perl and CGI don't require a screen-scraper. CGI understands HTTP. You can write a POJO (Plain Old Java Object) and make HTTP call to the FFM.
Originally posted by zheng shu:
Talking about "requirement" here![]()
"place the customer on hold" means that the agent has to hold
the customer on the phone (playing music to themand moves
to the shared computer to work with the FFM system, getting
the points redeemed. That is what it means. So you see, here
it is a manual process. You new system is supposed to automate
the process.
You can not change the protocol used by FFM because that is
the requirement that FFM remains unchanged. I can only tell
you (otherwise, it will be removedthat FFM talks only HTTP
and that is what language your system has to talk in. How awkard
it is, that is the sole language it understands.