Number of request handlers

Kyle_Baley

Have done some tweaking here and there but am about to embark on a full-fledged request handler. I'm hoping to get some advice on my approach.The functionality: Have a page where the user enters a number, then have Livelink create that number of Physical Object files in a certain folder with default values.I was thinking of using three request handlers for this: one to get the input, one to create the files and one to display the results. The second one would create the files then set the .fLocation to the third handler so that the user doesn't accidentally trigger the creation process twice by hitting refresh.Does this sound reasonable? If so, I'd like to pass the first and last unique ID to the third handler so I can report this to the user. What's the best way to do this?Thanks,Kyle

Hans Stoop

Message from Hans Stoop via eLinkSounds reasonable.For passing the information to the 3rd request handler, you have ingeneral 2 options, an din this case I would go for the first one:1. Pass the data in the URL to the third RH.2. Store the data in the cache table and pass via the URL the ID of thecache entry.I don't know how many objects will be created and of there is apossibility that the browser times out on the request. In that case youcan return from the second RH midway via the browserbegone function.Search the LL code for details. In this case you should pass theinformation via the cache table (method 2).Hans> -----Original Message-----> From: eLink Discussion: Development Discussion > [mailto:development@elinkkc.opentext.com] > Sent: vrijdag 1 september 2006 19:43> To: eLink Recipient> Subject: Number of request handlers> > Number of request handlers> Posted by Rome, Libby on 09/01/2006 01:40 PM> > Have done some tweaking here and there but am about to embark > on a full-fledged request handler. I'm hoping to get some > advice on my approach.> > The functionality: Have a page where the user enters a > number, then have Livelink create that number of Physical > Object files in a certain folder with default values.> > I was thinking of using three request handlers for this: one > to get the input, one to create the files and one to display > the results. The second one would create the files then set > the .fLocation to the third handler so that the user doesn't > accidentally trigger the creation process twice by hitting refresh.> > Does this sound reasonable? If so, I'd like to pass the first > and last unique ID to the third handler so I can report this > to the user. What's the best way to do this?> > Thanks,> Kyle> > [To reply to this thread, use your normal E-mail reply function.]> > ============================================================> > Discussion: Development Discussion> https://knowledge.opentext.com/knowledge/llisapi.dll/open/786303> > Livelink Server:> https://knowledge.opentext.com/knowledge/llisapi.dll> > To Unsubscribe from this Discussion, send an e-mail to > unsubscribe.development@elinkkc.opentext.com.> > >